Triple
T15178911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Antarctic Survey topographic maps |
E362685
|
entity |
| Predicate | datumUsed |
P117022
|
FINISHED |
| Object | WGS84 (recent editions) |
—
|
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: WGS84 (recent editions) | Statement: [British Antarctic Survey topographic maps, datumUsed, WGS84 (recent editions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datumUsed Context triple: [British Antarctic Survey topographic maps, datumUsed, WGS84 (recent editions)]
-
A.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
B.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
C.
designationUse
Indicates how a particular designation or title is intended to be used or applied in relation to an entity.
-
D.
denUse
Indicates that an entity uses or makes use of a particular den (or designated shelter/space) for its activities or habitation.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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_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. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:09 a.m.