Triple
T3512984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumatran rhinoceros |
E74238
|
entity |
| Predicate | mostThreatenedAmong |
P6220
|
FINISHED |
| Object | living rhinoceros species |
—
|
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: living rhinoceros species | Statement: [Sumatran rhinoceros, mostThreatenedAmong, living rhinoceros species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostThreatenedAmong Context triple: [Sumatran rhinoceros, mostThreatenedAmong, living rhinoceros species]
-
A.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
B.
primaryThreat
Indicates that one entity is the main or most significant source of danger, harm, or risk to another entity.
-
C.
inDangerSince
Indicates that an entity has been in a state of danger continuously starting from a specified point in time.
-
D.
rankedAmong
chosen
Indicates that an entity holds a specific position or status within a defined group, list, or hierarchy of comparable entities.
-
E.
deadliestIn
Indicates that something has the highest lethality or causes the most deaths within a specified context, group, or location.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc2d0bf481909d1f19a87d147b63 |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.