Triple
T37876871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formics |
E944747
|
entity |
| Predicate | threatPerceptionByHumans |
P108659
|
FINISHED |
| Object | existential threat |
—
|
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: existential threat | Statement: [Formics, threatPerceptionByHumans, existential threat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatPerceptionByHumans Context triple: [Formics, threatPerceptionByHumans, existential threat]
-
A.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
B.
perceivedThreat
chosen
Indicates that one entity regards another entity or situation as potentially harmful, dangerous, or adverse.
-
C.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
D.
threatEncounteredNear
Indicates that a threat was encountered in close spatial proximity to a specified reference point or entity.
-
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.
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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:19 p.m.