Triple
T23032073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Taipei Olympic Committee |
E573488
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | CTOC |
—
|
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: CTOC | Statement: [Chinese Taipei Olympic Committee, abbreviation, CTOC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CTOC Context triple: [Chinese Taipei Olympic Committee, abbreviation, CTOC]
-
A.
CTOC
chosen
CTOC is the abbreviation commonly used for the Chinese Taipei Olympic Committee, the organization responsible for overseeing Olympic sports and athletes representing Chinese Taipei.
-
B.
KTOC
KTOC is the ICAO airport code for Toccoa Airport – R.G. Letourneau Field in Georgia, United States.
-
C.
TOC
TOC is the abbreviation for the Tri-State Oversight Committee, an intergovernmental body that oversees safety and regulatory compliance for certain regional transit systems.
-
D.
TOC
TOC is the IATA airport code for Toccoa Airport – R.G. Letourneau Field in Georgia, United States.
-
E.
TOC
TOC (Talk to OSCAR) is a simplified, publicly documented protocol once used by AOL Instant Messenger clients to communicate with AOL’s messaging servers.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f184822a90819081907d72c76770b0 |
completed | April 29, 2026, 4:09 a.m. |
Created at: April 17, 2026, 3:53 p.m.