Triple
T32200444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English Theatre Company in Paris |
E822516
|
entity |
| Predicate | performedAuthor |
P139866
|
FINISHED |
| Object | William Shakespeare |
—
|
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: William Shakespeare | Statement: [English Theatre Company in Paris, performedAuthor, William Shakespeare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedAuthor Context triple: [English Theatre Company in Paris, performedAuthor, William Shakespeare]
-
A.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
B.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or entity.
-
C.
performedTextBy
chosen
Indicates that a text-based work (such as a script, lyrics, or written piece) is realized or executed as a performance by a specific performer or group.
-
D.
performed
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
E.
performedFrom
Indicates that an action or operation is carried out starting at or originating from a specified source location, context, or entity.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 1, 2026, 12:36 a.m.