Triple
T8442711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hà Nam Province |
E199585
|
entity |
| Predicate | distanceToDescription |
P7750
|
FINISHED |
| Object | approximately 60 km south of Hà Nội |
—
|
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: approximately 60 km south of Hà Nội | Statement: [Hà Nam Province, distanceToDescription, approximately 60 km south of Hà Nội]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDescription Context triple: [Hà Nam Province, distanceToDescription, approximately 60 km south of Hà Nội]
-
A.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
distance
chosen
Indicates the spatial separation or length between two points, objects, or locations.
-
C.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
D.
distanceFromReading
Indicates the measured spatial distance between a specified entity and the location of Reading.
-
E.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe310d8e08190b871bda79acde678 |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.