Triple
T28295030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pazzo! |
E713539
|
entity |
| Predicate | hasMemberOfPerformingDuo |
P128910
|
FINISHED |
| Object | Neil Tennant |
—
|
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: Neil Tennant | Statement: [Pazzo!, hasMemberOfPerformingDuo, Neil Tennant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberOfPerformingDuo Context triple: [Pazzo!, hasMemberOfPerformingDuo, Neil Tennant]
-
A.
hasNotablePerformerDuo
Indicates that the subject has a notable performing duo associated with it, such as a well-known pair of artists or entertainers who perform together.
-
B.
artistDuoMember
chosen
Indicates that one entity is a member of a specific artist duo.
-
C.
performedByDuoFrom
Indicates that an action or performance is carried out by a duo whose origin or affiliation is from a specified place or source.
-
D.
formedDuoWith
Indicates that two entities joined together to create a duo, typically collaborating or acting as a pair for a shared purpose or activity.
-
E.
hasTwinActors
Indicates that two or more actors share a twin relationship, typically portraying twin characters or being treated as twins within a given context.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 11:31 p.m.