Triple
T28966446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furnish-John |
E732051
|
entity |
| Predicate | familyNameOfChildOf |
P175247
|
FINISHED |
| Object | Elton John |
—
|
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: Elton John | Statement: [Furnish-John, familyNameOfChildOf, Elton John]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNameOfChildOf Context triple: [Furnish-John, familyNameOfChildOf, Elton John]
-
A.
familyNameOfMembers
Indicates that the specified family name is shared by the members of a given group or family.
-
B.
familyNameRefersTo
Indicates that a specified family name designates or refers to a particular person, group, or lineage.
-
C.
familyNameDerivedFrom
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
-
D.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
-
E.
adoptedFamilyName
Indicates that an entity has taken or been given a family name different from their original one, typically through adoption, marriage, or personal choice.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 28, 2026, 8:52 a.m.