Triple
T17887575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vandal Savage |
E447235
|
entity |
| Predicate | hasLivedFor |
P2042
|
FINISHED |
| Object | thousands of years |
—
|
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: thousands of years | Statement: [Vandal Savage, hasLivedFor, thousands of years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivedFor Context triple: [Vandal Savage, hasLivedFor, thousands of years]
-
A.
livedBefore
Indicates that one entity existed or was alive at an earlier time than another entity.
-
B.
hasAdultLifeIn
Indicates that an entity spends or experiences its adult stage of life within a specified location or environment.
-
C.
livedDuring
Indicates that the subject existed or was alive at some point within the time period or lifespan associated with the object.
-
D.
hasLifetimeStatus
Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
-
E.
hasAge
chosen
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c14c4348190bb77712d9eae1d51 |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.