Triple
T18417480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge Theatre |
E441931
|
entity |
| Predicate | hasFlexibleStaging |
P131528
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bridge Theatre, hasFlexibleStaging, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlexibleStaging Context triple: [Bridge Theatre, hasFlexibleStaging, true]
-
A.
isStagedBy
Indicates that something (such as a performance, event, or production) is organized, directed, or put on by a particular agent or entity.
-
B.
staging
Indicates the process of arranging, organizing, or setting up elements in preparation for a main event, performance, or deployment.
-
C.
optionalStage
Indicates that a particular stage in a process, workflow, or sequence is not mandatory and may be included or skipped without invalidating the overall structure.
-
D.
stagingStyle
Indicates how an event, performance, or scene is arranged, presented, or visually organized in a given context.
-
E.
supportsStageManager
Indicates that one entity provides compatibility or functionality required for another entity to use or run Stage Manager.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a291f148190b289b5b617077797 |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 10:47 a.m.