Triple
T26837692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROC |
E675681
|
entity |
| Predicate | teamNameFormat |
P48350
|
FINISHED |
| Object | three-letter code ROC instead of RUS |
—
|
LITERAL FINISHED |
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: three-letter code ROC instead of RUS | Statement: [ROC, teamNameFormat, three-letter code ROC instead of RUS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamNameFormat Context triple: [ROC, teamNameFormat, three-letter code ROC instead of RUS]
-
A.
teamFormat
Indicates the structural arrangement or configuration in which a team is organized or operates.
-
B.
teamNameType
chosen
Indicates the type or category associated with a team's name (e.g., formal name, short name, nickname).
-
C.
teamName
Indicates the relationship that assigns or associates a specific name with a particular team.
-
D.
teamNameRefersTo
Indicates that a given team name designates or refers to a specific team entity.
-
E.
teamFormatHistory
Indicates the historical record of changes or versions in a team's structural or competitive format over time.
- F. None of above.
Provenance (3 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61b43c03c8190a0ef7e5fd6ee70a4 |
completed | May 2, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:05 a.m.