Triple
T33526287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McFly family |
E858647
|
entity |
| Predicate | familyPatriarchInOriginal1985 |
P187404
|
FINISHED |
| Object | George McFly |
—
|
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: George McFly | Statement: [McFly family, familyPatriarchInOriginal1985, George McFly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyPatriarchInOriginal1985 Context triple: [McFly family, familyPatriarchInOriginal1985, George McFly]
-
A.
forefatherOf
Indicates that one person is an ancestor, typically from an earlier generation, of another person.
-
B.
fatherAlsoKnownAs
Indicates that a person’s father is known or referred to by an alternative name or alias.
-
C.
fatherInLawInPlot
Indicates that one person is the father-in-law of another within the context of a specific plot or storyline.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
fatherNotableRole
Indicates that the subject’s father is known for holding a particular notable role, position, or function.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 1, 2026, 1:39 a.m.