Triple
T36546118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gates of Sirion |
E901143
|
entity |
| Predicate | guardedAgainst |
P101950
|
FINISHED |
| Object | forces of Morgoth |
—
|
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: forces of Morgoth | Statement: [Gates of Sirion, guardedAgainst, forces of Morgoth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedAgainst Context triple: [Gates of Sirion, guardedAgainst, forces of Morgoth]
-
A.
guardedIn
Indicates that one entity is protected or kept under watch within the bounds or premises of another entity.
-
B.
guardedAs
Indicates that one entity is protected, watched over, or kept secure in the role or capacity specified by another entity.
-
C.
securedAgainst
chosen
Indicates that one entity is protected or safeguarded against threats, risks, or harmful actions originating from another entity or source.
-
D.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
protectedFor
Indicates that something is safeguarded or preserved specifically for the benefit, use, or rights of a particular entity or purpose.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.