Triple
T7754420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSA |
E175853
|
entity |
| Predicate | associatedWithCallsign |
P1565
|
FINISHED |
| Object | CSA-LINES |
E175854
|
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: CSA-LINES | Statement: [CSA, associatedWithCallsign, CSA-LINES]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CSA-LINES Context triple: [CSA, associatedWithCallsign, CSA-LINES]
-
A.
CSA-LINES
chosen
CSA-LINES is the radio callsign used by Czech Airlines for its flight operations and air traffic communications.
-
B.
CSA
CSA is the ICAO airline designator used to identify Czech Airlines in international aviation operations.
-
C.
CSA
CSA is a U.S. Federal Motor Carrier Safety Administration initiative that monitors and enforces commercial motor vehicle safety performance to reduce crashes, injuries, and fatalities.
-
D.
CSA
CSA is the College Squash Association, the governing body that oversees intercollegiate squash competition and regulations in the United States.
-
E.
CSA
CSA is the Canadian Soccer Association, the national governing body responsible for overseeing soccer in Canada, including its youth and senior national teams.
- 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c703d851d4819091e9117d3f34cb9a |
completed | March 27, 2026, 10:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8be5dbf5881908d07d70c8ae061a5 |
completed | March 29, 2026, 5:53 a.m. |
Created at: March 27, 2026, 4:08 p.m.