Triple
T10871183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EKBO |
E256656
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | EKBO |
E256656
|
NE 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: EKBO | Statement: [EKBO, abbreviation, EKBO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EKBO Context triple: [EKBO, abbreviation, EKBO]
-
A.
EKBO
chosen
EKBO is the German abbreviation for the Evangelical Church of Berlin-Brandenburg-Silesian Upper Lusatia, a regional Protestant church body within the Evangelical Church in Germany (EKD).
-
B.
EK
EK was the New York Stock Exchange ticker symbol for Eastman Kodak Company, the historic American photography and imaging corporation.
-
C.
EK
EK is the commonly used abbreviation for the First Chamber of the Austrian Parliament (Erste Kammer).
-
D.
EKB
EKB is the National Rail station code for Eskbank railway station in Midlothian, Scotland.
-
E.
EBOS
EBOS is the ICAO airport code for Ostend–Bruges International Airport in Belgium, a regional hub for cargo and passenger flights.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75186e75c8190bf046ea666faff54 |
completed | April 9, 2026, 7:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7dbea28819083511b56bcd7d4ce |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 8, 2026, 9:20 p.m.