Triple
T29692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mojave Desert tortoise |
E592
|
entity |
| Predicate | maximumLifespan |
P585
|
FINISHED |
| Object | over 80 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: over 80 years | Statement: [Mojave Desert tortoise, maximumLifespan, over 80 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumLifespan Context triple: [Mojave Desert tortoise, maximumLifespan, over 80 years]
-
A.
lifespan
chosen
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
B.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context or system.
-
C.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
-
D.
termLength
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490019948190a89bb0910c60d462 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a2486d40348190b2d21fc444f499a6 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.