Triple
T31863115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dance 'Til We're High |
E813383
|
entity |
| Predicate | hasMemberProducer |
P196876
|
FINISHED |
| Object | Youth |
—
|
NE NERFINISHED |
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: Youth | Statement: [Dance 'Til We're High, hasMemberProducer, Youth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberProducer Context triple: [Dance 'Til We're High, hasMemberProducer, Youth]
-
A.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
-
B.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
C.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
D.
hasMembersWith
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
-
E.
hasAssociateMember
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fe6c7fc4388190aa88993d00872d7f |
completed | May 8, 2026, 11:06 p.m. |
Created at: April 30, 2026, 11:53 p.m.