Triple
T7540248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankee Harbour |
E178255
|
entity |
| Predicate | hasSurroundingTopography |
P53384
|
FINISHED |
| Object | low-lying coastal terrain |
—
|
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: low-lying coastal terrain | Statement: [Yankee Harbour, hasSurroundingTopography, low-lying coastal terrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingTopography Context triple: [Yankee Harbour, hasSurroundingTopography, low-lying coastal terrain]
-
A.
hasTopographicContext
chosen
Indicates that one entity is related to or characterized by a particular topographic or physical landscape context.
-
B.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
C.
hasNearbyPlateau
Indicates that one geographic entity is located close to or adjacent to a plateau.
-
D.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
-
E.
hasMountainousTerrain
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f873b17081908bb70aea0010d072 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.