Triple
T16365277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gogot language |
E397419
|
entity |
| Predicate | likelyEndangered |
P123122
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Gogot language, likelyEndangered, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyEndangered Context triple: [Gogot language, likelyEndangered, true]
-
A.
isEndangeredDueTo
Indicates that an entity is endangered as a result of the specific cause or factor represented by the related entity.
-
B.
areEndangeredOrVulnerable
Indicates that the entities are classified as being at risk of extinction, either endangered or vulnerable, according to conservation status criteria.
-
C.
possiblyExtinctBy
Indicates that an entity is believed or suspected to have gone extinct as a result of the specified cause or agent.
-
D.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
E.
endangerment
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
- F. None of above. chosen
Provenance (4 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff3c915c81909e1757fc31921876 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.