Triple
T33526290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McFly family |
E858647
|
entity |
| Predicate | ancestralLineIncludes |
P101267
|
FINISHED |
| Object | Seamus 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: Seamus McFly | Statement: [McFly family, ancestralLineIncludes, Seamus McFly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralLineIncludes Context triple: [McFly family, ancestralLineIncludes, Seamus McFly]
-
A.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
B.
ancestralLinks
chosen
Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
-
C.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
-
D.
isDescendantLineOf
Indicates that one entity is connected to another through a direct or indirect line of descent, such as child, grandchild, or further generational lineage.
-
E.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
- F. None of above.
Provenance (3 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_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:39 a.m.