Triple
T21399358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS Explorer OL12 |
E527868
|
entity |
| Predicate | mapCodePrefix |
P143823
|
FINISHED |
| Object | OL |
—
|
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: OL | Statement: [OS Explorer OL12, mapCodePrefix, OL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapCodePrefix Context triple: [OS Explorer OL12, mapCodePrefix, OL]
-
A.
icaoRegionPrefix
Indicates the regional ICAO prefix that designates the geographic or administrative region associated with an aviation-related entity.
-
B.
tailCodePrefix
Indicates that one entity’s tail code begins with, or is prefixed by, the string represented by the other entity.
-
C.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
-
D.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
E.
hasAirportCodePrefix
Indicates that an airport’s code begins with a specified sequence of characters.
- 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b16d9f008190bbf6199ff6952cb3 |
completed | April 22, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:14 p.m.