Triple
T856457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huai River |
E18501
|
entity |
| Predicate | usedAsBoundaryFor |
P15022
|
FINISHED |
| Object | heating policy line in China |
—
|
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: heating policy line in China | Statement: [Huai River, usedAsBoundaryFor, heating policy line in China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBoundaryFor Context triple: [Huai River, usedAsBoundaryFor, heating policy line in China]
-
A.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
B.
setsBoundary
chosen
Indicates that one entity defines or forms the limiting edge or border of another entity.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
hasBoundaryType
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
E.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac3c172481908ed164ee1579ec28 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.