Triple
T34125400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pin Up Girl |
E875260
|
entity |
| Predicate | featuresMusicalNumbers |
P203969
|
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: [Pin Up Girl, featuresMusicalNumbers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMusicalNumbers Context triple: [Pin Up Girl, featuresMusicalNumbers, yes]
-
A.
hasMusicalNumberIn
Indicates that a musical number (song or performance) appears within or is featured in a specific work, scene, or production.
-
B.
hasMusicalNumberOrder
Indicates the sequential position of a musical number within a larger performance or work.
-
C.
featuresDanceNumber
Indicates that the subject includes or presents a dance performance or choreographed dance sequence.
-
D.
featuredInDanceNumbersWith
Indicates that two entities are prominently included together in one or more dance numbers within a performance or production.
-
E.
broadwayMusicalNumber
Indicates that one entity is a specific musical number (song or performance piece) that appears within a Broadway musical production represented by the other entity.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0301289dbc8190a4372958d3451171 |
completed | May 12, 2026, 10:30 a.m. |
| PD | Predicate disambiguation | batch_6a0300d4185c8190a383d5da3659bc4f |
completed | May 12, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_6a030127f5ec8190add78cf709b57611 |
completed | May 12, 2026, 10:30 a.m. |
Created at: May 1, 2026, 1:53 a.m.