Triple
T25711360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne |
E644738
|
entity |
| Predicate | ageRelativeToGroup |
P125146
|
FINISHED |
| Object | youngest |
—
|
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: youngest | Statement: [Anne, ageRelativeToGroup, youngest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRelativeToGroup Context triple: [Anne, ageRelativeToGroup, youngest]
-
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.
hasRelativeAge
Indicates that one entity has an age that is defined or compared in relation to the age of another entity.
-
C.
relativeAgeInference
Indicates an inferred ordering of ages between entities, specifying which one is relatively older or younger based on available information.
-
D.
ageGroupInvolved
Indicates that a particular age group participates in, is affected by, or is otherwise involved in the specified event or relationship.
-
E.
ageGroupSystem
Indicates a classification relationship where entities are grouped according to a defined system of age-based categories.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc157d9c819096b30f09438e351a |
completed | May 2, 2026, 1:28 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 9:14 p.m.