Triple
T33956112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekhof Theatre |
E870576
|
entity |
| Predicate | hasOriginalFeature |
P196799
|
FINISHED |
| Object | historic stage machinery |
—
|
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: historic stage machinery | Statement: [Ekhof Theatre, hasOriginalFeature, historic stage machinery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalFeature Context triple: [Ekhof Theatre, hasOriginalFeature, historic stage machinery]
-
A.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
B.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
C.
hasOriginalPart
Indicates that an entity includes a component or segment that is part of its initial, original composition.
-
D.
originalFeature
Indicates that one entity is the initial or source feature from which another feature is derived, modified, or referenced.
-
E.
hasOriginalLocation
Indicates that an entity was initially located or situated at a specified place or position before any change or movement occurred.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
| PDg | Predicate description generation | batch_69fe68a385f48190b942700e3eddc9b6 |
completed | May 8, 2026, 10:50 p.m. |
Created at: May 1, 2026, 1:49 a.m.