Triple
T20251825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Reaches |
E498574
|
entity |
| Predicate | directionFromMainLine |
P97479
|
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: [Northern Reaches, directionFromMainLine, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromMainLine Context triple: [Northern Reaches, directionFromMainLine, north]
-
A.
connectsToMainLineAt
Indicates that one entity is linked or joined to a primary or central line at a specific point.
-
B.
directionFromMainLands
chosen
Indicates the cardinal or relative direction in which something is located or extends from the main lands.
-
C.
isOnNorthSideMainLine
Indicates that something is located on the north side of the main line.
-
D.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
E.
frontLineDirection
Indicates the primary orientation or bearing in which the front line of a conflict, formation, or boundary is facing or advancing.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a8b8488190b344df7a65f59684 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.