Triple
T18448157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halling dance |
E450709
|
entity |
| Predicate | performedSoloOrGroup |
P72860
|
FINISHED |
| Object | solo |
—
|
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: solo | Statement: [Halling dance, performedSoloOrGroup, solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedSoloOrGroup Context triple: [Halling dance, performedSoloOrGroup, solo]
-
A.
performedIndividually
chosen
Indicates that the action or activity was carried out by a single individual rather than collaboratively or as part of a group.
-
B.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
C.
performsSongWith
Indicates that two or more entities jointly perform or present a song together.
-
D.
performedInFormation
Indicates that an action or event was carried out while participants were arranged in a specific, organized formation.
-
E.
performedSongFor
Indicates that one entity performed a song specifically for another entity as the intended audience or recipient.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52645cb88819086b0e70b6613edcd |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.