Triple
T29958589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNCO |
E760976
|
entity |
| Predicate | announcedDisbandment |
P4650
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [CNCO, announcedDisbandment, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedDisbandment Context triple: [CNCO, announcedDisbandment, 2022]
-
A.
disbandsAfter
Indicates that one entity ceases to exist or formally dissolves at some point following the occurrence or completion of another entity or event.
-
B.
announcedHiatus
Indicates that an entity has publicly declared a temporary pause or suspension in its usual activities or operations.
-
C.
announcedThat
chosen
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
D.
disbandedDueTo
Indicates that an organization, group, or entity ceased to exist specifically as a result of a particular cause, event, or condition.
-
E.
reasonForDisbandment
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 6:28 p.m.