Triple
T21427963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uzhavoor |
E528610
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | KL |
—
|
NE NERFINISHED |
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: KL | Statement: [Uzhavoor, vehicleRegistrationCode, KL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KL Context triple: [Uzhavoor, vehicleRegistrationCode, KL]
-
A.
KL
KL is the two-letter IATA airline code assigned to KLM Royal Dutch Airlines.
-
B.
KL
chosen
KL is the official vehicle registration code assigned to the Indian state of Kerala.
-
C.
KL
KL is the squadron code historically used to identify No. 54 Squadron of the Royal Air Force on its aircraft and operational records.
-
D.
KL
KL is the abbreviation commonly used for the Royal Netherlands Army, the land forces branch of the Dutch Armed Forces.
-
E.
KL
KL is the station code used to identify the Berlin U-Bahn station Krumme Lanke.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b3e74bcc81909ad66e3c59152ffc |
completed | April 22, 2026, 11:41 a.m. |
Created at: April 16, 2026, 5:49 p.m.