Triple
T18261643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Saigon (original London production direction) |
E437370
|
entity |
| Predicate | runType |
P85647
|
FINISHED |
| Object | long-running West End production |
—
|
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: long-running West End production | Statement: [Miss Saigon (original London production direction), runType, long-running West End production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runType Context triple: [Miss Saigon (original London production direction), runType, long-running West End production]
-
A.
runnerType
Indicates the specific category or style of running associated with an entity (e.g., sprinter, marathoner, trail runner).
-
B.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
C.
originalRunType
chosen
Indicates the initial or primary category or mode under which a particular run, execution, or process was originally conducted.
-
D.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
-
E.
runsDirection
Indicates that an entity moves or operates in a specified direction.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff76a1208190abbe6ab8720ed154 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.