Triple
T17649170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maaroom |
E429438
|
entity |
| Predicate | distanceToGreatSandyStrait |
P128392
|
FINISHED |
| Object | direct waterfront access |
—
|
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: direct waterfront access | Statement: [Maaroom, distanceToGreatSandyStrait, direct waterfront access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGreatSandyStrait Context triple: [Maaroom, distanceToGreatSandyStrait, direct waterfront access]
-
A.
distanceToGreatBarrierReef
Indicates the spatial distance between a given entity and the Great Barrier Reef.
-
B.
distanceToTofino_km
Indicates the distance, measured in kilometers, between a given location and Tofino.
-
C.
approximateDistanceFromAnchorage
Indicates the estimated spatial distance between a given entity and Anchorage, rather than an exact measured value.
-
D.
distanceToPacificOcean
Indicates the physical distance between a given location or entity and the Pacific Ocean.
-
E.
distanceToForster_km
Indicates the physical distance, measured in kilometers, between an entity and a reference location named Forster.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e3bc2f8819092e3365d9e798386 |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 6:05 a.m.