Triple
T15178897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Antarctic Survey topographic maps |
E362685
|
entity |
| Predicate | featureTypeShown |
P41649
|
FINISHED |
| Object | contours |
—
|
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: contours | Statement: [British Antarctic Survey topographic maps, featureTypeShown, contours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureTypeShown Context triple: [British Antarctic Survey topographic maps, featureTypeShown, contours]
-
A.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
B.
displaysFeature
chosen
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
-
C.
featureTypeCatalog
Indicates that an entity is associated with, or defined by, a catalog that specifies the types of features it can include or reference.
-
D.
featureLayer
Indicates that one entity functions as a feature layer associated with, or used within, another entity (such as a map, dataset, or visualization context).
-
E.
featuresStyle
Indicates that one entity exhibits, incorporates, or is characterized by a particular style associated with another entity.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00663b4148190b647592eda315d1d |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.