Triple
T7611033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Marlowe Theatre |
E172235
|
entity |
| Predicate | hasSecondarySpace |
P77763
|
FINISHED |
| Object | studio theatre |
—
|
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: studio theatre | Statement: [The Marlowe Theatre, hasSecondarySpace, studio theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondarySpace Context triple: [The Marlowe Theatre, hasSecondarySpace, studio theatre]
-
A.
hasSecondaryCore
Indicates that an entity possesses an additional, subordinate core component alongside its primary core.
-
B.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
-
C.
hasSecondaryBase
Indicates that an entity possesses or is associated with a secondary or additional base, distinct from its primary base.
-
D.
hasSecondaryFocus
Indicates that an entity has an additional, subordinate area of attention, concern, or specialization beyond its primary focus.
-
E.
hasSecondaryPool
Indicates that an entity possesses an additional, non-primary pool or reservoir associated with it.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa221c848190b892ba1caec8d83a |
completed | March 27, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8195e5c8190835e28d44e19f6ef |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:55 p.m.