Triple
T34989627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thorn |
E1009343
|
entity |
| Predicate | isSignificantCityOf |
P9892
|
FINISHED |
| Object | Black Marsh |
—
|
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: Black Marsh | Statement: [Thorn, isSignificantCityOf, Black Marsh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSignificantCityOf Context triple: [Thorn, isSignificantCityOf, Black Marsh]
-
A.
isMetropolitanOf
Indicates that one entity is the primary metropolitan area or major urban center associated with another entity, such as a region, country, or administrative division.
-
B.
isMajorCityIn
chosen
Indicates that a city is a primary or significant urban center located within a specified larger region or country.
-
C.
isCity
Indicates that the subject entity is classified as a city.
-
D.
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).
-
E.
locatedInCityWithSignificance
Indicates that an entity is located in a city that holds particular importance or notable significance (e.g., historical, cultural, political, or economic).
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.