Triple
T30160842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auf Wiederseh’n Sweetheart |
E766659
|
entity |
| Predicate | hasNotablePerformerNationality |
P3285
|
FINISHED |
| Object | British |
—
|
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: British | Statement: [Auf Wiederseh’n Sweetheart, hasNotablePerformerNationality, British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePerformerNationality Context triple: [Auf Wiederseh’n Sweetheart, hasNotablePerformerNationality, British]
-
A.
performingArtistNationality
chosen
Indicates the nationality or country of origin of the artist who performs a given work or performance.
-
B.
hasPerformerContinent
Indicates that the performer involved in an event or work is associated with a specific continent.
-
C.
performerLaterNationality
Indicates that the performer acquired or held this nationality at a later point in their life, after an earlier or original nationality.
-
D.
hasCastMemberNationality
Indicates that at least one cast member of a work has the specified nationality.
-
E.
hasLeadActorNationality
Indicates that the nationality of the lead actor in a work is a specified country or nationality.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
Created at: April 29, 2026, 7:21 p.m.