Triple
T7413529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heihe |
E171068
|
entity |
| Predicate | geographicalDirectionInChina |
P46910
|
FINISHED |
| Object | northeast |
—
|
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: northeast | Statement: [Heihe, geographicalDirectionInChina, northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicalDirectionInChina Context triple: [Heihe, geographicalDirectionInChina, northeast]
-
A.
geographicDirectionWithinCountry
chosen
Indicates that one place lies in a specified cardinal or intercardinal direction relative to another place within the same country.
-
B.
geographicDirectionImpliedByName
Indicates that the name of a place or feature suggests a specific geographic direction (e.g., north, south, east, west) relative to some reference.
-
C.
travelsDirection
Indicates that an entity moves or is transported in a specified directional heading or orientation.
-
D.
geographicDirectionWithinState
Indicates that one location lies in a specified cardinal or relative geographic direction within the boundaries of a particular state.
-
E.
roadDirectionConvention
Indicates the customary rule in a place for which side of the road vehicles are expected to drive on.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c336308190932c14cec5eec25f |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.