Triple
T31163788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freshen Up tour |
E794414
|
entity |
| Predicate | tourPersonnel |
P7128
|
FINISHED |
| Object | Paul McCartney – vocals, bass, guitar, piano |
—
|
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: Paul McCartney – vocals, bass, guitar, piano | Statement: [Freshen Up tour, tourPersonnel, Paul McCartney – vocals, bass, guitar, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourPersonnel Context triple: [Freshen Up tour, tourPersonnel, Paul McCartney – vocals, bass, guitar, piano]
-
A.
personnelComposition
Indicates the makeup or distribution of people or roles within a group, organization, or unit.
-
B.
touringTeam
Indicates that a team is traveling to different locations to play matches or perform in a series of scheduled events.
-
C.
peakPersonnel
Indicates the maximum number of personnel involved or present at any point during a specified period or activity.
-
D.
notablePersonnel
chosen
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
-
E.
tourRole
Indicates the specific function, capacity, or responsibility an entity has within the context of a tour.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:07 p.m.