Triple
T22244850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA country code system |
E549814
|
entity |
| Predicate | hasExampleCode |
P30248
|
FINISHED |
| Object | SCO |
—
|
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: SCO | Statement: [FIFA country code system, hasExampleCode, SCO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SCO Context triple: [FIFA country code system, hasExampleCode, SCO]
-
A.
SCO
chosen
SCO is the official FIFA country code used to represent the Scotland national football team in international competitions and records.
-
B.
SCO
SCO is a Eurasian political, economic, and security alliance led by China and Russia that promotes regional cooperation among its member states.
-
C.
SCO
SCO is the official three-letter abbreviation used for the Perth Scorchers, a professional Twenty20 cricket team based in Perth, Western Australia.
-
D.
SCO
SCO (Sharable Content Object) is a reusable, self-contained unit of e-learning content designed to be tracked and delivered within SCORM-compliant learning management systems.
-
E.
SCO
SCO is the California State Controller’s Office, the state agency responsible for overseeing and accounting for California’s public funds.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132170e5081909b9dbb204abf2a45 |
completed | April 28, 2026, 10:17 p.m. |
Created at: April 16, 2026, 8:38 p.m.