Triple
T9969471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ally Maine |
E195764
|
entity |
| Predicate | hasStagePerformance |
P83295
|
FINISHED |
| Object | performs Shallow on stage with Jackson Maine |
—
|
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: performs Shallow on stage with Jackson Maine | Statement: [Ally Maine, hasStagePerformance, performs Shallow on stage with Jackson Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStagePerformance Context triple: [Ally Maine, hasStagePerformance, performs Shallow on stage with Jackson Maine]
-
A.
hasLivePerformanceWith
chosen
Indicates that two or more entities participate together in the same live performance event.
-
B.
hasFanPerformances
Indicates that an entity has associated performances created or carried out by fans.
-
C.
hasStageAppearance
Indicates that an entity makes or has made a performance or appearance on a stage, typically before an audience.
-
D.
hasLivePerformanceStyle
Indicates that an entity is associated with a particular style or manner of live performance.
-
E.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b7ea9881908a56f11e2e446dd0 |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:47 p.m.