Triple
T6633026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shangdu |
E149972
|
entity |
| Predicate | hasInnerCity |
P71849
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shangdu, hasInnerCity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInnerCity Context triple: [Shangdu, hasInnerCity, yes]
-
A.
isInlandCity
Indicates that a city is located away from the coast, without direct access to the sea or ocean.
-
B.
isInnerCityRoad
Indicates that a road is located within and primarily serves the inner (central, densely built-up) area of a city.
-
C.
withinUrbanArea
Indicates that one entity is located inside the spatial boundaries of an urban area associated with another entity.
-
D.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
-
E.
isCoreCity
Indicates that a city serves as a primary, central, or most important urban area within a larger region, system, or network.
- 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_69c687ee50048190aa151765bef16193 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c30733908190980f7ffaa5c5527b |
completed | March 27, 2026, 5:48 p.m. |
Created at: March 27, 2026, 1:59 p.m.