Triple
T37369493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gate of Writhen Iron |
E927799
|
entity |
| Predicate | guardedCity |
P187786
|
FINISHED |
| Object | Gondolin |
—
|
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: Gondolin | Statement: [Gate of Writhen Iron, guardedCity, Gondolin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedCity Context triple: [Gate of Writhen Iron, guardedCity, Gondolin]
-
A.
guardedIn
Indicates that one entity is protected or kept under watch within the bounds or premises of another entity.
-
B.
cityTypeGuarded
chosen
Indicates that a city is protected or defended by some form of guard, military presence, or protective force.
-
C.
cityHeld
Indicates that a particular city was the location where an event, activity, or occurrence took place or was hosted.
-
D.
ruledCity
Indicates that a person or governing entity exercised political authority or control over a specific city.
-
E.
passesCity
Indicates that a route, path, or journey goes through or traverses a particular city as part of its course.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.