Triple
T29118028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrietta Lange |
E737100
|
entity |
| Predicate | worksWithInFiction |
P176006
|
FINISHED |
| Object | G. Callen |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: G. Callen | Statement: [Henrietta Lange, worksWithInFiction, G. Callen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksWithInFiction Context triple: [Henrietta Lange, worksWithInFiction, G. Callen]
-
A.
worksUnderInFiction
Indicates that, within a fictional context or narrative, one character or entity is hierarchically subordinate to and takes direction from another.
-
B.
workInFiction
Indicates that one entity is a fictional work in which the other entity appears or is set.
-
C.
worksInFictionalContext
Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
-
D.
usedInFictionalWork
Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
-
E.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 28, 2026, 11:23 a.m.