Triple
T37369513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gate of Writhen Iron |
E927799
|
entity |
| Predicate | rulerOfCityGuarded |
P60298
|
FINISHED |
| Object | Turgon |
—
|
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: Turgon | Statement: [Gate of Writhen Iron, rulerOfCityGuarded, Turgon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulerOfCityGuarded Context triple: [Gate of Writhen Iron, rulerOfCityGuarded, Turgon]
-
A.
ruledCity
Indicates that a person or governing entity exercised political authority or control over a specific city.
-
B.
rulerOf
chosen
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
C.
primaryDefendedCity
Indicates that an entity served as the main or principal city that another entity was responsible for defending.
-
D.
positionHeldByDefendedRulerType
Indicates a relationship where a specific position or office is held by a ruler whose type or category is characterized as being defended or protected.
-
E.
rulerDeity
Indicates that a deity holds supreme governing or sovereign authority over a realm, people, or cosmic domain.
- 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_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.