Triple
T34949567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norseman, Western Australia |
E1007951
|
entity |
| Predicate | distanceToEsperance |
P103068
|
FINISHED |
| Object | approximately 200 kilometres 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: approximately 200 kilometres north | Statement: [Norseman, Western Australia, distanceToEsperance, approximately 200 kilometres north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToEsperance Context triple: [Norseman, Western Australia, distanceToEsperance, approximately 200 kilometres north]
-
A.
hasApproxDistanceFromEsperance
chosen
Indicates that one entity is located at an approximate distance from the reference location Esperance.
-
B.
distanceToSeptÎles
Indicates the measured distance between a given entity and the location of Sept-Îles.
-
C.
distanceFromJuanFernandezIslands_km
Indicates the distance, measured in kilometers, between an entity and the Juan Fernández Islands.
-
D.
distanceToTristanDaCunha
Indicates the spatial distance between a given entity and Tristan da Cunha.
-
E.
distanceToLeHavre
Indicates the spatial distance between a given entity and the location of Le Havre.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.