Triple
T16268456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lopingian Epoch |
E394934
|
entity |
| Predicate | terrestrialFauna |
P950
|
FINISHED |
| Object | diverse therapsid assemblages |
—
|
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: diverse therapsid assemblages | Statement: [Lopingian Epoch, terrestrialFauna, diverse therapsid assemblages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrestrialFauna Context triple: [Lopingian Epoch, terrestrialFauna, diverse therapsid assemblages]
-
A.
fauna
chosen
Indicates that an entity is an animal or part of the animal life associated with a particular place or context.
-
B.
hasTerrestrialHabitat
Indicates that an entity lives primarily on land or in a ground-based environment rather than in aquatic or aerial habitats.
-
C.
dominantLargeTerrestrialVertebrates
Indicates that the referenced entities are the primary or most ecologically influential large land-dwelling vertebrate animals in a given context or environment.
-
D.
faunaDiversity
Indicates the variety and richness of animal species present within a given area or ecosystem.
-
E.
faunaOrigin
Indicates the place or source from which an animal species or population originates.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245ca5c708190a1e98ab37740c032 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.