Triple
T33267146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Close to Me |
E851681
|
entity |
| Predicate | hasDanceOrientedProduction |
P166200
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Close to Me, hasDanceOrientedProduction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDanceOrientedProduction Context triple: [Close to Me, hasDanceOrientedProduction, true]
-
A.
hasDanceFocusedProduction
chosen
Indicates that a production is primarily centered on or dedicated to dance as its main artistic focus.
-
B.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
C.
hasDancePerformancesBy
Indicates that one entity features or includes dance performances carried out by another entity.
-
D.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
E.
hasDanceMovement
Indicates that one entity includes, performs, or is characterized by a specific dance movement associated with another entity.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:32 a.m.