Triple
T4498222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Plymouth |
E100750
|
entity |
| Predicate | hasCoastalWalkwayLength |
P32976
|
FINISHED |
| Object | approximately 13 km |
—
|
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 13 km | Statement: [New Plymouth, hasCoastalWalkwayLength, approximately 13 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalWalkwayLength Context triple: [New Plymouth, hasCoastalWalkwayLength, approximately 13 km]
-
A.
shorelineLength
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
-
B.
hasCoastalPath
chosen
Indicates that there exists a designated path or route running along or adjacent to the coastline of a given area or feature.
-
C.
isWaterfrontThoroughfare
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
-
D.
isCoastalPark
Indicates that a park is located along or directly adjacent to a coastline.
-
E.
navigableLengthApproxKm
Indicates the approximate distance, measured in kilometers, over which something (typically a waterway) can be navigated.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56c065e88190934eb0b1632d79bb |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.