Triple
T27699648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hulan District |
E698392
|
entity |
| Predicate | geographicalDirectionFromHarbinCenter |
P28261
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Hulan District, geographicalDirectionFromHarbinCenter, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicalDirectionFromHarbinCenter Context triple: [Hulan District, geographicalDirectionFromHarbinCenter, north]
-
A.
directionFromHamilton
Indicates the directional relationship of one location as measured outward starting from Hamilton.
-
B.
distanceFromCityCenterDirection
Indicates the distance and compass direction of a location relative to the center of a specified city.
-
C.
directionFromCityCenter
chosen
Indicates the compass direction in which one location lies relative to the city center.
-
D.
geographicDirectionWithinCountry
Indicates that one place lies in a specified cardinal or intercardinal direction relative to another place within the same country.
-
E.
geographicalDirectionInProvince
Indicates that one place lies in a specified geographical direction within the boundaries of a given province.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 2:56 p.m.