Triple
T5408164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS Landranger 89 |
E120944
|
entity |
| Predicate | hasContourInformation |
P40118
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [OS Landranger 89, hasContourInformation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContourInformation Context triple: [OS Landranger 89, hasContourInformation, true]
-
A.
hasColorInfo
Indicates that an entity is associated with specific color-related information or attributes.
-
B.
hasSilhouetteShape
chosen
Indicates that one entity has the overall outline or contour shape specified or characterized by another entity.
-
C.
hasTopographicContext
Indicates that one entity is related to or characterized by a particular topographic or physical landscape context.
-
D.
hasNumberOfPoints
Indicates that an entity is associated with a specific count of points it possesses or comprises.
-
E.
hasUncertainOuterBoundary
Indicates that the outer boundary of an entity is not precisely defined, fixed, or clearly determined.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8794e0c4819082bebf2da5e41201 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.