Triple
T28443670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marshall Gregson |
E715778
|
entity |
| Predicate | originalRunEndOfWork |
P198161
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Marshall Gregson, originalRunEndOfWork, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRunEndOfWork Context triple: [Marshall Gregson, originalRunEndOfWork, 2011]
-
A.
originalRunStartOfWork
Indicates that the referenced time or event marks the initial, unmodified starting point of a particular work activity or process.
-
B.
originalRunEndNetwork
Indicates the network or system in which an original run, process, or sequence ultimately concludes or terminates.
-
C.
originalWestEndRunEnd
Indicates the date or point in time when a production’s original run in London’s West End concluded.
-
D.
appearsAtEndOfWork
Indicates that an entity occurs or is presented at the conclusion or final portion of a work.
-
E.
originalRunDay
Indicates the specific day on which something (such as an event, program, or process) was first run or initially executed.
- F. None of above. chosen
Provenance (4 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
| PDg | Predicate description generation | batch_69feced436a48190b761db7df2d6b6bd |
completed | May 9, 2026, 6:06 a.m. |
Created at: April 28, 2026, 1:47 a.m.