Triple
T35198312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Neiman |
E1016328
|
entity |
| Predicate | returnsToStageWith |
P45021
|
FINISHED |
| Object | Terence Fletcher |
—
|
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: Terence Fletcher | Statement: [Andrew Neiman, returnsToStageWith, Terence Fletcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsToStageWith Context triple: [Andrew Neiman, returnsToStageWith, Terence Fletcher]
-
A.
returnToStage
Indicates that an entity goes back onto a stage or performance area after having left it.
-
B.
returnsAsGhostTo
Indicates that an entity comes back after death in the form of a ghost to another entity or location.
-
C.
returnsTo
chosen
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
D.
usesStage
Indicates that one entity employs or operates on another entity at a particular phase or stage within a process or workflow.
-
E.
usedStage
Indicates that an entity made use of a particular stage or phase within a process, workflow, or lifecycle.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:02 p.m.