Triple
T17985295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bali tiger |
E430214
|
entity |
| Predicate | humanThreat |
P50110
|
FINISHED |
| Object | sport hunting |
—
|
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: sport hunting | Statement: [Bali tiger, humanThreat, sport hunting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanThreat Context triple: [Bali tiger, humanThreat, sport hunting]
-
A.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
B.
threatType
chosen
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
D.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
E.
laterThreat
Indicates that one entity poses a threat to another at a time subsequent to some referenced or initial point.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29a27b081909a128a6b978eabf8 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.