Triple
T11397788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mba languages |
E270023
|
entity |
| Predicate | areEndangeredOrVulnerable |
P99092
|
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: [Mba languages, areEndangeredOrVulnerable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areEndangeredOrVulnerable Context triple: [Mba languages, areEndangeredOrVulnerable, true]
-
A.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
B.
areEndangeredInPart
Indicates that an entity is endangered only in certain regions or parts of its overall range, rather than throughout its entire distribution.
-
C.
hasConservationConcernIn
Indicates that an entity is subject to a specified conservation concern status within a particular geographic area or jurisdiction.
-
D.
conservationStatus
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
-
E.
endangeredMembers
Indicates that the members of a group, category, or population are at risk of extinction or serious harm.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80019d3d48190a2f473deb6eae33a |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.