Triple
T37468136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhinocs |
E931081
|
entity |
| Predicate | collectiveThreat |
P196405
|
FINISHED |
| Object | Dangerous in large numbers |
—
|
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: Dangerous in large numbers | Statement: [Rhinocs, collectiveThreat, Dangerous in large numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveThreat Context triple: [Rhinocs, collectiveThreat, Dangerous in large numbers]
-
A.
globalThreats
Indicates a relationship where certain entities pose or are associated with dangers or risks that have worldwide or cross-border impact.
-
B.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
C.
universeThreat
Indicates that an entity poses a danger or existential risk to the entire universe.
-
D.
threatsFaced
Indicates that an entity is exposed to or experiences specific dangers, risks, or harmful conditions.
-
E.
threatTypeDeterrence
Indicates a relationship where a threat is characterized specifically as serving a deterrent function, aimed at discouraging or preventing certain actions or behaviors.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69fe30bb07d08190877539d5aa202d24 |
completed | May 8, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:17 p.m.