Triple
T38678878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noel Gay |
E943830
|
entity |
| Predicate | wroteForPerformer |
P42811
|
FINISHED |
| Object | George Formby |
—
|
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: George Formby | Statement: [Noel Gay, wroteForPerformer, George Formby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteForPerformer Context triple: [Noel Gay, wroteForPerformer, George Formby]
-
A.
writtenForPerformer
chosen
Indicates that a work was specifically composed or created to be performed by a particular performer or type of performer.
-
B.
workWrittenFor
Indicates that a creative work was specifically composed, produced, or created for a particular person, group, event, purpose, or medium.
-
C.
hasWrittenSongsFor
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by another entity.
-
D.
coWroteSongRecordedBy
Indicates that two or more entities jointly authored a song that was later recorded by a specified performer or group.
-
E.
hasWritingCreditOn
Indicates that an entity is credited as a writer or co-writer for a particular work or production.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.