Triple
T36693587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vlamingh Head Lighthouse |
E906025
|
entity |
| Predicate | locationRelativeToTown |
P179191
|
FINISHED |
| Object | north of Exmouth |
—
|
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 of Exmouth | Statement: [Vlamingh Head Lighthouse, locationRelativeToTown, north of Exmouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToTown Context triple: [Vlamingh Head Lighthouse, locationRelativeToTown, north of Exmouth]
-
A.
positionRelativeToTown
chosen
Indicates the spatial position or orientation of one place or object in relation to a specified town.
-
B.
locationRelativeToMajorCity
Indicates the spatial relationship or position of a place in reference to a nearby major city.
-
C.
locationRelativeToLargestCity
Indicates how a place is spatially positioned or oriented in relation to the largest city in a given area or region.
-
D.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other entity.
-
E.
locationRelativeToIP
Indicates a spatial or geographic relationship between an entity and a given IP address’s inferred location.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.