Triple
T16617263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conselh de la Lenga Occitana |
E403726
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | CLO |
E403726
|
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: CLO | Statement: [Conselh de la Lenga Occitana, abbreviation, CLO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CLO Context triple: [Conselh de la Lenga Occitana, abbreviation, CLO]
-
A.
CLO
chosen
CLO is the acronym for the Conselh de la Lenga Occitana, the official body responsible for regulating and standardizing the Occitan language.
-
B.
CLO
CLO is the IATA airport code for Alfonso Bonilla Aragón International Airport, the main airport serving Cali, Colombia.
-
C.
Tailo
Tailo is a widely used Latin-based romanization system for writing Taiwanese Hokkien, employed in education, literature, and language preservation.
-
D.
COS
COS is the College of Science at Northeastern University, encompassing disciplines such as biology, chemistry, physics, mathematics, and related scientific fields.
-
E.
COS
COS is the French Armed Forces' elite joint command responsible for planning and conducting special operations.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754ac9dc8190965197024594742b |
completed | April 18, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007daef18481908c3628a3466300ce |
completed | May 10, 2026, 12:44 p.m. |
Created at: April 10, 2026, 5:17 a.m.