Triple
T20892921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lystrosaurus |
E514451
|
entity |
| Predicate | likelyLifestyle |
P51691
|
FINISHED |
| Object | terrestrial |
—
|
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: terrestrial | Statement: [Lystrosaurus, likelyLifestyle, terrestrial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyLifestyle Context triple: [Lystrosaurus, likelyLifestyle, terrestrial]
-
A.
lifestyle
Indicates that an entity’s way of living or habitual behaviors are associated with, influence, or characterize another entity or outcome.
-
B.
lifeHabit
chosen
Indicates the typical way an organism lives or behaves in its environment, such as its mode of life, activity pattern, or ecological lifestyle.
-
C.
supportsLifestyle
Indicates that one entity provides the resources, conditions, or assistance necessary for another entity to maintain a particular way of living.
-
D.
likelyBehavior
Indicates the behavior or action that an entity is expected or predicted to exhibit under given circumstances.
-
E.
lifestyleFeature
Indicates that one entity offers, includes, or is characterized by a particular lifestyle-related amenity, attribute, or quality for another entity.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05fecd88190905a0ea80a24406a |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.