Triple
T29028672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dances of the League of David |
E737664
|
entity |
| Predicate | containsDancePieces |
P141994
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dances of the League of David, containsDancePieces, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDancePieces Context triple: [Dances of the League of David, containsDancePieces, yes]
-
A.
hasDanceEnsemble
Indicates that an entity is associated with or includes a particular dance ensemble as part of its activities or composition.
-
B.
containsDanceNumber
chosen
Indicates that something (such as a work, performance, or production) includes at least one distinct dance sequence or dance number as part of its content.
-
C.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
D.
hasDancePerformancesBy
Indicates that one entity features or includes dance performances carried out by another entity.
-
E.
hasDanceFormation
Indicates that an entity participates in or is arranged into a specific dance formation.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 28, 2026, 9:54 a.m.