Triple
T5970364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church House, Westminster |
E132855
|
entity |
| Predicate | hasAlternativeUse |
P32842
|
FINISHED |
| Object | commercial events venue |
—
|
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: commercial events venue | Statement: [Church House, Westminster, hasAlternativeUse, commercial events venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeUse Context triple: [Church House, Westminster, hasAlternativeUse, commercial events venue]
-
A.
isAlsoUsedAs
chosen
Indicates that something serves an additional function or role beyond its primary one.
-
B.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
-
C.
hasAlternativeReferent
Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
-
D.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
E.
hasAlternateCut
Indicates that an entity has an alternative edited version or cut, distinct from its primary or original form.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03e174c7c8190b04113f6529f5f0e |
completed | March 22, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69c0335b55a48190927a5b1529edb542 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:03 p.m.