Triple
T33373339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangerously in Love Tour |
E854556
|
entity |
| Predicate | includesGroupMaterial |
P204041
|
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: [Dangerously in Love Tour, includesGroupMaterial, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesGroupMaterial Context triple: [Dangerously in Love Tour, includesGroupMaterial, yes]
-
A.
materialGroup
Indicates a classification relationship where an entity is assigned to a specific group based on the material it is made of or associated with.
-
B.
usesMaterialBy
Indicates that one entity makes use of or employs a material that is provided, specified, or created by another entity.
-
C.
isMaterialSpecific
Indicates that a relationship, rule, or property applies only to a particular material or set of materials, rather than being generally applicable.
-
D.
includesSoloMaterial
Indicates that a work or collection contains material performed or created by a single individual rather than a group or ensemble.
-
E.
includesDuetMaterial
Indicates that the referenced item contains material specifically written or arranged for a duet performance.
- F. None of above. chosen
Provenance (4 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a031045669c8190944781a48d09b5b6 |
completed | May 12, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_6a030fa775848190839b388f950d0364 |
completed | May 12, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_6a031044b88481909092553ee4198fd5 |
completed | May 12, 2026, 11:34 a.m. |
Created at: May 1, 2026, 1:35 a.m.