Triple
T29723400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wall of Life project |
E752117
|
entity |
| Predicate | opposesThreatType |
P149086
|
FINISHED |
| Object | monstrous threats |
—
|
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: monstrous threats | Statement: [Wall of Life project, opposesThreatType, monstrous threats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposesThreatType Context triple: [Wall of Life project, opposesThreatType, monstrous threats]
-
A.
threatsDefendedAgainst
chosen
Indicates a relationship where one entity protects another from specific dangers, attacks, or harmful actions.
-
B.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
C.
isThreatenedCategory
Indicates that an entity belongs to a category facing risk of harm, decline, or extinction.
-
D.
hasThreatType
Indicates that an entity is associated with, or characterized by, a specific type or category of threat.
-
E.
hasThreats
Indicates that one entity poses or is associated with potential danger, harm, or adverse consequences toward another entity.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 28, 2026, 7:37 p.m.