Triple
T14638507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay of Dragons |
E343664
|
entity |
| Predicate | inWorldGeography |
P115169
|
FINISHED |
| Object | east of the Dothraki Sea |
—
|
LITERAL FINISHED |
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: east of the Dothraki Sea | Statement: [Bay of Dragons, inWorldGeography, east of the Dothraki Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inWorldGeography Context triple: [Bay of Dragons, inWorldGeography, east of the Dothraki Sea]
-
A.
impliesGeographicalFact
Indicates that one geographical statement or condition logically entails the truth of another geographical fact.
-
B.
geographicalPractice
Indicates a relationship where an entity engages in or is associated with a practice, activity, or method that is specific to or characteristic of a particular geographic area or location.
-
C.
worldName
Indicates that an entity has or is associated with a specific world’s name.
-
D.
continentFound
Indicates that a specified continent is the location where a particular entity is found or occurs.
-
E.
continentType
Indicates that one entity is classified as a specific type or category of continent in relation to another entity.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4aca6448190adf1042dfbfef716 |
completed | April 14, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:26 a.m.