Triple
T31448675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Espada |
E802257
|
entity |
| Predicate | oftenDancedBy |
P172541
|
FINISHED |
| Object | principal male dancer |
—
|
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: principal male dancer | Statement: [Espada, oftenDancedBy, principal male dancer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDancedBy Context triple: [Espada, oftenDancedBy, principal male dancer]
-
A.
oftenDancedIn
Indicates that an entity frequently performed dancing activities within or at the location or context specified by another entity.
-
B.
alsoDancedAs
Indicates that an entity performed under an additional dance name or identity besides their primary one.
-
C.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
D.
hasDancePerformancesBy
chosen
Indicates that one entity features or includes dance performances carried out by another entity.
-
E.
hasDanceEnsemble
Indicates that an entity is associated with or includes a particular dance ensemble as part of its activities or composition.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 30, 2026, 9:11 p.m.