Triple
T5436309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javan rhinoceros |
E122014
|
entity |
| Predicate | captiveStatus |
P50271
|
FINISHED |
| Object | no known individuals in captivity |
—
|
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: no known individuals in captivity | Statement: [Javan rhinoceros, captiveStatus, no known individuals in captivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captiveStatus Context triple: [Javan rhinoceros, captiveStatus, no known individuals in captivity]
-
A.
detaineeStatus
Indicates the current legal or custodial condition of a person being detained, such as whether they are in custody, released, or under a specific detention regime.
-
B.
availabilityStatus
chosen
Indicates the current state of whether something is obtainable, usable, or accessible at a given time.
-
C.
locationStatus
Indicates the current state or condition of an entity with respect to a specific location (e.g., present, absent, en route, or unknown).
-
D.
landerStatus
Indicates the current operational or situational state of a lander in its mission lifecycle.
-
E.
securityStatus
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.