Triple
T31734795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Set in Darkness |
E809962
|
entity |
| Predicate | isSetInCity |
P12399
|
FINISHED |
| Object | Edinburgh |
—
|
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: Edinburgh | Statement: [Set in Darkness, isSetInCity, Edinburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSetInCity Context triple: [Set in Darkness, isSetInCity, Edinburgh]
-
A.
isInCity
chosen
Indicates that one entity is located within the geographical boundaries of a specified city.
-
B.
isCityOf
Indicates that one entity is a city that belongs to, is located within, or is administratively part of another entity (such as a country, state, or region).
-
C.
isCity
Indicates that the subject entity is classified as a city.
-
D.
usedInCity
Indicates that something is utilized, applied, or operates within the context or boundaries of a particular city.
-
E.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab22f464819098766f11b1c3c846 |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:23 p.m.