Triple
T19211297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tactical Technology Office |
E480361
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | TTO |
—
|
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: TTO | Statement: [Tactical Technology Office, abbreviation, TTO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TTO Context triple: [Tactical Technology Office, abbreviation, TTO]
-
A.
TTO
TTO is the FIFA country code representing the Trinidad and Tobago national football team in international competitions.
-
B.
TTO
chosen
TTO is a DARPA office focused on developing and demonstrating high-risk, high-payoff advanced military technologies and systems.
-
C.
TBO
TBO is the IATA airport code for Tabora Airport, a regional airport serving the town of Tabora in Tanzania.
-
D.
NTOV
NTOV is an independent record label associated with the releases of Icelandic composer Jóhann Jóhannsson.
-
E.
TOG
TOG is the commonly used abbreviation for The Open Group, an international consortium that develops open, vendor-neutral technology standards and certifications.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa365c2481909b3c36ebae18265d |
completed | April 20, 2026, 10:04 a.m. |
Created at: April 10, 2026, 1:21 p.m.