Triple
T857003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chersina angulata |
E18513
|
entity |
| Predicate | foundInHabitat |
P6481
|
FINISHED |
| Object | coastal scrub |
—
|
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: coastal scrub | Statement: [Chersina angulata, foundInHabitat, coastal scrub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInHabitat Context triple: [Chersina angulata, foundInHabitat, coastal scrub]
-
A.
foundInRegion
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
B.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
C.
inhabitedBy
chosen
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
D.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
E.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac4d47508190b48d944aa2d881bf |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.