Triple
T29958590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNCO |
E760976
|
entity |
| Predicate | finalTour |
P44658
|
FINISHED |
| Object |
Última Cita Tour
Última Cita Tour is CNCO’s farewell concert tour marking the Latin boy band’s final series of live performances before disbanding.
|
E1892475
|
NE 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: Última Cita Tour | Statement: [CNCO, finalTour, Última Cita Tour]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Última Cita Tour Triple: [CNCO, finalTour, Última Cita Tour]
Generated description
Última Cita Tour is CNCO’s farewell concert tour marking the Latin boy band’s final series of live performances before disbanding.
Provenance (5 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_69f6783c19d081909aa0691853c370de |
completed | May 2, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2714398f448190a8f06a98a4e008d9 |
completed | June 8, 2026, 7:12 p.m. |
| NEDg | Description generation | batch_6a2714e0a8e48190bcebb7601fc3b4e8 |
completed | June 8, 2026, 7:15 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a271968eae08190834668e2da3cd703 |
completed | June 8, 2026, 7:35 p.m. |
Created at: April 29, 2026, 6:28 p.m.