Triple
T478664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colo-Colo |
E9116
|
entity |
| Predicate | domesticTitleType |
P6489
|
FINISHED |
| Object | Primera División de Chile championships |
—
|
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: Primera División de Chile championships | Statement: [Colo-Colo, domesticTitleType, Primera División de Chile championships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticTitleType Context triple: [Colo-Colo, domesticTitleType, Primera División de Chile championships]
-
A.
titleType
chosen
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
B.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
C.
hasTitleInLaw
Indicates that an entity holds or is designated by a specific formal title as defined or recognized in law.
-
D.
titleNumber
Indicates the numerical designation or sequence number assigned to a title within an ordered set of titles.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f056459881909749764cc4a7f9e8 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf017548190ae38ff3314a1ffa3 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.