Triple
T6308569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Käina |
E141439
|
entity |
| Predicate | countryCode |
P208
|
FINISHED |
| Object | EE |
E520195
|
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: EE | Statement: [Käina, countryCode, EE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EE Context triple: [Käina, countryCode, EE]
-
A.
EE
chosen
EE is the two-letter country code for Estonia, a Northern European nation on the Baltic Sea.
-
B.
EE
EE is a major British mobile network operator and internet service provider known for its extensive 4G and 5G coverage across the UK.
-
C.
EE
The EE was a former New York City Subway service that operated on the BMT Broadway Line, primarily providing local service in Manhattan and Queens before being discontinued.
-
D.
EEE
EEE is the internal BBC production code assigned to the Doctor Who serial "Terror of the Autons."
-
E.
ECE
ECE is the Explicit Congestion Experienced flag used in IP and TCP headers to indicate network congestion without dropping packets, as defined in RFC 3168’s ECN mechanism.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0647d38008190abaf96632712ddf9 |
completed | March 22, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e45330ec8190945682962ae823b0 |
completed | March 27, 2026, 1:58 a.m. |
Created at: March 22, 2026, 4:28 p.m.