Triple
T37411165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geraldton–Mount Magnet Road |
E929572
|
entity |
| Predicate | hasInlandEndpoint |
P203046
|
FINISHED |
| Object | Mount Magnet |
—
|
NE NERFINISHED |
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: Mount Magnet | Statement: [Geraldton–Mount Magnet Road, hasInlandEndpoint, Mount Magnet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInlandEndpoint Context triple: [Geraldton–Mount Magnet Road, hasInlandEndpoint, Mount Magnet]
-
A.
isInlandPort
Indicates that a port facility is located inland, away from the open sea, typically on a river, canal, or lake, while still serving maritime or shipping functions.
-
B.
hasEndpointLocation
Indicates that something has a specific location at which it terminates or reaches its end point.
-
C.
hasEndpointCountry
Indicates that an entity such as a route, connection, or infrastructure element terminates or has an endpoint located in a specified country.
-
D.
hasInlandCity
Indicates that one entity has, contains, or is associated with a city located inland (away from the coast or major bodies of water).
-
E.
hasEndpointCity
Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01185c46f0819089b4a2ad3c3e2f33 |
completed | May 10, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_6a0117e19e008190870663dd45084416 |
completed | May 10, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_6a01185b580c8190a01f65404486cfec |
completed | May 10, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:16 p.m.