Triple
T10323620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lina Leandersson as Eli |
E242701
|
entity |
| Predicate | actualAge |
P61009
|
FINISHED |
| Object | over 200 years old |
—
|
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: over 200 years old | Statement: [Lina Leandersson as Eli, actualAge, over 200 years old]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualAge Context triple: [Lina Leandersson as Eli, actualAge, over 200 years old]
-
A.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
B.
representedAgeLevel
Indicates that one entity corresponds to, or is categorized under, a particular age level or age group.
-
C.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
-
D.
yearTurned
Indicates the specific year in which an entity changed state, status, or classification (e.g., when it became, reached, or turned into something).
-
E.
ageDetail
chosen
Indicates a detailed specification of an entity’s age, such as exact value, range, or related age attributes.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:50 a.m.