Triple
T37671275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elena Lincoln |
E937962
|
entity |
| Predicate | ageRelativeToChristianGrey |
P125146
|
FINISHED |
| Object | older than Christian Grey |
—
|
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: older than Christian Grey | Statement: [Elena Lincoln, ageRelativeToChristianGrey, older than Christian Grey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRelativeToChristianGrey Context triple: [Elena Lincoln, ageRelativeToChristianGrey, older than Christian Grey]
-
A.
ageRelativeToVincentChase
Indicates how an entity’s age compares to the age of Vincent Chase (e.g., younger, older, or the 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.
ageInSeries
Indicates the age of an entity as it appears or is depicted within a specific series or installment of a work.
-
D.
ageDuringNarration
Indicates that an entity has a specified age at the time when the described narrative or event is taking place.
-
E.
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).
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e5be808190aa4e01219b36df80 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.