Triple
T30134166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobias Haslinger |
E765938
|
entity |
| Predicate | familyRelationTypeWithCarl Haslinger |
P178613
|
FINISHED |
| Object | father |
—
|
LITERAL FINISHED |
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: father | Statement: [Tobias Haslinger, familyRelationTypeWithCarl Haslinger, father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRelationTypeWithCarl Haslinger Context triple: [Tobias Haslinger, familyRelationTypeWithCarl Haslinger, father]
-
A.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
B.
relationshipTypeWithJohnHartigan
Indicates the specific nature or category of relationship that an entity has with John Hartigan.
-
C.
worksInCloseRelationshipWith
Indicates a collaborative professional relationship in which two or more entities work together closely and interact frequently to achieve shared goals.
-
D.
familyRelationToCharltons
Indicates the type of familial relationship an entity has to the Charltons.
-
E.
hasRelationshipTypeWith Alexandra Bergson
Indicates that there exists a specific type or category of relationship between an entity and Alexandra Bergson.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 29, 2026, 7:16 p.m.