Triple
T28890660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Gate of Mordor |
E732683
|
entity |
| Predicate | defensivePurpose |
P113160
|
FINISHED |
| Object | to bar entry into Mordor |
—
|
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: to bar entry into Mordor | Statement: [Black Gate of Mordor, defensivePurpose, to bar entry into Mordor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensivePurpose Context triple: [Black Gate of Mordor, defensivePurpose, to bar entry into Mordor]
-
A.
defensiveUse
Indicates that an entity uses something primarily for protection or defense against threats or attacks.
-
B.
hasDefensivePurpose
chosen
Indicates that something exists or is designed with the primary goal of protection, defense, or safeguarding against threats or harm.
-
C.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
D.
defensiveTactics
Indicates the use or implementation of strategies, maneuvers, or methods intended to protect, guard, or defend against threats or attacks.
-
E.
defensiveSide
Indicates which entity is acting in a defensive role or position relative to another entity or situation.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 7:54 a.m.