Triple
T33217331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabilgathol |
E850321
|
entity |
| Predicate | neighbourCitySindarinName |
P177611
|
FINISHED |
| Object | Nogrod |
—
|
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: Nogrod | Statement: [Gabilgathol, neighbourCitySindarinName, Nogrod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighbourCitySindarinName Context triple: [Gabilgathol, neighbourCitySindarinName, Nogrod]
-
A.
SindarinName
Indicates that one entity is the Sindarin (Elvish) name or designation of another entity.
-
B.
isShireSeatOf
Indicates that a location serves as the administrative center or county town (shire seat) for a given shire or county.
-
C.
KhuzdulName
Indicates that an entity bears a name expressed in the Khuzdul (Dwarvish) language.
-
D.
nameInQuenya
Indicates that an entity has a specific name expressed in the Quenya language.
-
E.
associatedCityNameTransliteration
Indicates that an entity is linked to a city whose name is given in a transliterated (phonetic or romanized) form.
- F. None of above. chosen
Provenance (4 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:30 a.m.