Triple
T25387474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yum-Yum |
E631563
|
entity |
| Predicate | onStageRelationship |
P26739
|
FINISHED |
| Object | Pitti-Sing |
—
|
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: Pitti-Sing | Statement: [Yum-Yum, onStageRelationship, Pitti-Sing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onStageRelationship Context triple: [Yum-Yum, onStageRelationship, Pitti-Sing]
-
A.
relatesStage
Indicates that one entity is associated with, occurs in, or pertains to a particular stage or phase within a process, lifecycle, or sequence.
-
B.
stageRelation
Indicates a relationship between entities based on their roles, positions, or phases within a staged process or sequence.
-
C.
associatedWithStageName
Indicates that an entity is connected to or known by a particular stage name used as an alternate professional identity.
-
D.
performerRelationshipContext
chosen
Indicates the contextual nature or circumstances of the relationship between a performer and another entity (such as an event, work, or role).
-
E.
sceneRelationship
Indicates a contextual or spatial relationship that links entities based on how they co-occur or interact within the same scene.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5656c16ac8190be99d40cb63f9541 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:47 p.m.