Triple
T18509243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violet Plunkett |
E452288
|
entity |
| Predicate | relativeAgeDescriptor |
P94896
|
FINISHED |
| Object | teenage daughter |
—
|
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: teenage daughter | Statement: [Violet Plunkett, relativeAgeDescriptor, teenage daughter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeAgeDescriptor Context triple: [Violet Plunkett, relativeAgeDescriptor, teenage daughter]
-
A.
relativeAgeStatus
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.
relativeByBirth
Indicates that two entities are related to each other through a biological family connection established by birth.
-
D.
characterAgeDescriptor
chosen
Indicates how a character’s age is qualitatively described or categorized (e.g., young, middle-aged, elderly) rather than given as a specific number.
-
E.
timeRelativeToBirth
Indicates the temporal position of an event or state relative to an entity’s birth (e.g., before, at, or after birth).
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53344c6b081908e780ed5c815a766 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.