Triple
T29596724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tony |
E754319
|
entity |
| Predicate | primaryHumanRelationshipWith |
P203289
|
FINISHED |
| Object | Claire Belmont |
—
|
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: Claire Belmont | Statement: [Tony, primaryHumanRelationshipWith, Claire Belmont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHumanRelationshipWith Context triple: [Tony, primaryHumanRelationshipWith, Claire Belmont]
-
A.
primaryFamily
Indicates that one entity is the main or principal family unit to which another entity is most closely or formally associated.
-
B.
subjectFamilyRelation
Indicates that there is a familial relationship of some kind between the subject entity and another entity.
-
C.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
-
D.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
E.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a014a0b57dc8190b04ce51156ab95fa |
completed | May 11, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_6a0149afa57c8190a83257085766d916 |
completed | May 11, 2026, 3:14 a.m. |
| PDg | Predicate description generation | batch_6a014a0ab56c819082ce383fb5987654 |
completed | May 11, 2026, 3:16 a.m. |
Created at: April 28, 2026, 6:18 p.m.