Triple
T4490065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chesterfield Islands |
E107347
|
entity |
| Predicate | distanceToAustralia |
P56865
|
FINISHED |
| Object | approximately 800 km east of Queensland coast |
—
|
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 800 km east of Queensland coast | Statement: [Chesterfield Islands, distanceToAustralia, approximately 800 km east of Queensland coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAustralia Context triple: [Chesterfield Islands, distanceToAustralia, approximately 800 km east of Queensland coast]
-
A.
distanceFromSydney
Indicates the spatial distance between a given location and the city of Sydney.
-
B.
distanceToDarwin
Indicates the spatial distance between a given entity’s location and the location of Darwin.
-
C.
distanceToGoldCoast
Indicates the measured distance between a given entity and the location known as the Gold Coast.
-
D.
distanceToMelbourne
Indicates the spatial distance between a given location or entity and the city of Melbourne.
-
E.
distanceToBrisbane_km
Indicates the physical distance, measured in kilometers, between a given location and Brisbane.
- 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_69bd43f84f788190a1383579c4a595be |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd556d29f08190bab1e872dd7e819f |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 12:59 p.m.