Triple
T5152496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Express |
E116228
|
entity |
| Predicate | callsign |
P1565
|
FINISHED |
| Object | UNITED |
E259065
|
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: UNITED | Statement: [United Express, callsign, UNITED]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UNITED Context triple: [United Express, callsign, UNITED]
-
A.
UNITED
UNITED is the radio callsign used by pilots and air traffic control to identify and communicate with United Airlines flights.
-
B.
United
United is a common shorthand nickname for Leeds United F.C., the professional football club based in Leeds, West Yorkshire, England.
-
C.
United
chosen
United is the airline callsign used by United Airlines, one of the largest major carriers in the United States.
-
D.
UN
The UN is an international organization founded in 1945 that brings together most of the world’s countries to promote peace, security, cooperation, and human rights.
-
E.
UN
UN is the vehicle registration code for the German town of Unna in the state of North Rhine-Westphalia.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd78daab708190a42734a14dddb2fc |
completed | March 20, 2026, 4:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bed0099afc8190badca81bd5efb8f6 |
completed | March 21, 2026, 5:06 p.m. |
Created at: March 20, 2026, 1:44 p.m.