Triple
T29468772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvian Song and Dance Festival |
E747451
|
entity |
| Predicate | participantGroups |
P61730
|
FINISHED |
| Object | choirs |
—
|
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: choirs | Statement: [Latvian Song and Dance Festival, participantGroups, choirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantGroups Context triple: [Latvian Song and Dance Festival, participantGroups, choirs]
-
A.
participantGroup
chosen
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
-
B.
boardingGroups
Indicates that certain entities are assigned to or associated with specific boarding groups for an ordered boarding process.
-
C.
groupWithin
Indicates that one group is contained or nested as a subgroup within another, larger group.
-
D.
representedGroups
Indicates that an entity serves as an official or recognized representative for one or more groups.
-
E.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 3:55 p.m.