Triple
T33604228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Son |
E860803
|
entity |
| Predicate | distanceToMoss |
P205234
|
FINISHED |
| Object | approximately 20 km north of Moss |
—
|
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 20 km north of Moss | Statement: [Son, distanceToMoss, approximately 20 km north of Moss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMoss Context triple: [Son, distanceToMoss, approximately 20 km north of Moss]
-
A.
distanceFromMossman
Indicates the measured or specified distance between a given entity or location and Mossman.
-
B.
distanceFromMossVale
Indicates the spatial distance between an entity and the reference location Moss Vale.
-
C.
distanceToMold
Indicates the measured or estimated spatial distance between an entity and a specified mold.
-
D.
hopDistance
Indicates the number of intermediate steps or "hops" required to traverse from one entity to another within a network or graph.
-
E.
distanceToHoverla
Indicates the measured distance between a given entity’s location and Hoverla.
- F. None of above. chosen
Provenance (4 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:41 a.m.