Triple
T4253145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Learner |
E95905
|
entity |
| Predicate | notablePerformanceMedium |
P54971
|
FINISHED |
| Object | costume performance |
—
|
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: costume performance | Statement: [David Learner, notablePerformanceMedium, costume performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePerformanceMedium Context triple: [David Learner, notablePerformanceMedium, costume performance]
-
A.
notableMedia
Indicates a relationship where a media work is recognized as significant, prominent, or especially relevant in connection with a given entity.
-
B.
notablePrimaryPerformance
Indicates that an entity is recognized for a primary or leading performance in a work or event.
-
C.
notableAdaptationPerformance
Indicates that an entity is recognized for a significant performance in an adaptation of another work.
-
D.
firstPerformanceMedium
Indicates the medium or format (e.g., stage, radio, television) in which a work was first performed.
-
E.
notableProgramType
Indicates that the subject is recognized for or associated with a particular type or category of program.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ebc98e08190915ac309a51ef87f |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:06 p.m.