Triple
T11394095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Lewis |
E269920
|
entity |
| Predicate | workAppearsInForm |
P36545
|
FINISHED |
| Object | Broadway play |
—
|
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: Broadway play | Statement: [George Lewis, workAppearsInForm, Broadway play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workAppearsInForm Context triple: [George Lewis, workAppearsInForm, Broadway play]
-
A.
appearsInSectionOfWork
Indicates that one entity is contained within or shows up in a specific section or part of a larger work.
-
B.
formOfWork
chosen
Indicates that one creative work is a specific form, version, or expression of another related work.
-
C.
settingOfWorkAppearsIn
Indicates that a particular place, time, or environment serves as the setting within which a given creative work’s events or narrative occur.
-
D.
employsForm
Indicates that an entity makes use of or applies a particular form or format in carrying out an action or function.
-
E.
hasWorkForm
Indicates that an entity is associated with a particular form, format, or mode in which its work or activity is carried out or expressed.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80018a58c81908b80dc9abd18d650 |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.