Triple
T20724403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tactical Air Command |
E509396
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | TAC |
—
|
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: TAC | Statement: [Tactical Air Command, nickname, TAC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TAC Context triple: [Tactical Air Command, nickname, TAC]
-
A.
TAC
TAC is the commonly used abbreviation for The Athletic Congress, the former governing body for track and field in the United States.
-
B.
TAC
TAC is the commonly used abbreviation for Tartu Art College, an Estonian institution of higher education specializing in art and design.
-
C.
TAC
TAC is the National Rail station code for Tackley railway station in Oxfordshire, England.
-
D.
TAC
TAC is the IATA airport code for Daniel Z. Romualdez Airport serving Tacloban City in the Philippines.
-
E.
TAC
chosen
TAC is the abbreviation for Tactical Air Command, a former major command of the United States Air Force responsible for tactical fighter, attack, and reconnaissance operations.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e662f08190917ee043612d413e |
completed | April 21, 2026, 12:16 a.m. |
Created at: April 16, 2026, 12:28 p.m.