Triple
T22972866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Austria |
E571234
|
entity |
| Predicate | ISOcountryCode |
P208
|
FINISHED |
| Object | AT |
—
|
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: AT | Statement: [Flag of Austria, ISOcountryCode, AT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AT Context triple: [Flag of Austria, ISOcountryCode, AT]
-
A.
AT
AT is the chassis designation used by the Scuderia AlphaTauri Formula One team for its race cars.
-
B.
AT
AT was the former stock ticker symbol under which the U.S. wireless telecommunications company Alltel was publicly traded.
-
C.
AT
chosen
AT is the two-letter ISO 3166-1 alpha-2 country code representing Austria.
-
D.
AT
AT is the commonly used abbreviation and public-facing brand name for Auckland Transport, the agency responsible for managing Auckland’s transport services and infrastructure.
-
E.
ATT
ATT is a telecommunications-related entity associated with the General Agreement on Tariffs and Trade (GATT), likely serving as a framework or mechanism within international trade and communications regulation.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182343a448190a5259cdf721c9d04 |
completed | April 29, 2026, 3:59 a.m. |
Created at: April 17, 2026, 3:48 p.m.