Triple
T5082829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Generation |
E114560
|
entity |
| Predicate | hasLiveStapleStatus |
P15281
|
FINISHED |
| Object | frequently performed in The Who concerts |
—
|
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: frequently performed in The Who concerts | Statement: [My Generation, hasLiveStapleStatus, frequently performed in The Who concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveStapleStatus Context triple: [My Generation, hasLiveStapleStatus, frequently performed in The Who concerts]
-
A.
hasLiveStapleStatusFor
chosen
Indicates that an entity currently holds an active or valid staple status for another entity or context.
-
B.
hasUnitStatus
Indicates that an entity is associated with a particular operational or condition status as a unit.
-
C.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
D.
hasLiveVersions
Indicates that an entity has one or more recorded or documented live-performance versions of itself.
-
E.
isStapleOf
Indicates that something is a basic or essential item regularly used or consumed within a particular context, place, 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74fb3df4819082bd8ae64e207ceb |
completed | March 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.