Triple
T32508760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sersi |
E830872
|
entity |
| Predicate | livesFor |
P90053
|
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: [Sersi, livesFor, thousands of years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesFor Context triple: [Sersi, livesFor, thousands of years]
-
A.
survivesFor
chosen
Indicates that one entity continues to exist, endure, or remain functional for a specified duration or period.
-
B.
heldForLife
Indicates that something is possessed, controlled, or held by an entity for the entire duration of that entity’s life, without transfer or expiration before death.
-
C.
livesAccordingTo
Indicates that an entity conducts its life or behavior in alignment with a specified principle, rule, belief system, or standard.
-
D.
isForLife
Indicates that something is intended to last or remain valid for the entire duration of a person’s or entity’s life.
-
E.
publicLife
Indicates that an entity is involved in activities, roles, or interactions that are conducted openly in the public sphere rather than in private life.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1 a.m.