Triple
T36817788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ash Mountains |
E909792
|
entity |
| Predicate | defensiveFunctionFor |
P187612
|
FINISHED |
| Object | Mordor |
—
|
NE NERFINISHED |
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: Mordor | Statement: [Ash Mountains, defensiveFunctionFor, Mordor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveFunctionFor Context triple: [Ash Mountains, defensiveFunctionFor, Mordor]
-
A.
defenseFunction
chosen
Indicates that an entity serves a protective or defensive role against threats, attacks, or harm to another entity or system.
-
B.
defensiveTask
Indicates a task in which an entity protects, guards, or defends another entity or resource from potential threats or harm.
-
C.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
D.
defensiveConcern
Indicates a relationship where one entity is worried about protecting itself or another from potential harm, threat, or criticism.
-
E.
defensiveUse
Indicates that an entity uses something primarily for protection or defense against threats or attacks.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.