Triple
T35286884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fritz Robinson |
E1019108
|
entity |
| Predicate | ageRelativeToSiblings |
P125146
|
FINISHED |
| Object | eldest son |
—
|
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: eldest son | Statement: [Fritz Robinson, ageRelativeToSiblings, eldest son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRelativeToSiblings Context triple: [Fritz Robinson, ageRelativeToSiblings, eldest son]
-
A.
relativeAgeStatus
chosen
Indicates a comparative relationship specifying how the age of one entity relates to the age of another (e.g., older, younger, or same age).
-
B.
relativeAgeInference
Indicates an inferred ordering of ages between entities, specifying which one is relatively older or younger based on available information.
-
C.
relativeByBirth
Indicates that two entities are related to each other through a biological family connection established by birth.
-
D.
hasRelativeAge
Indicates that one entity has an age that is defined or compared in relation to the age of another entity.
-
E.
ageRelation
Indicates a relationship that specifies or compares the ages of entities, such as one being older, younger, or of the same age as another.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fe35fd88190b2154c89e1b7ffd8 |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.