Triple
T36569109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSP |
E902065
|
entity |
| Predicate | operatesInBuildingUse |
P65370
|
FINISHED |
| Object | theatre 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: theatre venue | Statement: [GSP, operatesInBuildingUse, theatre venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInBuildingUse Context triple: [GSP, operatesInBuildingUse, theatre venue]
-
A.
currentBuildingUse
Indicates the present functional purpose or activity for which a building is being used.
-
B.
hasTypicalBuildingUse
Indicates that something is generally or normally used for a particular type of building function or purpose.
-
C.
locatedInBuildingUsedAs
chosen
Indicates that something is located inside a building that is being used for a specified purpose or function.
-
D.
appliesToBuildingComplex
Indicates that something (such as a rule, condition, attribute, or action) is relevant or applicable to an entire building complex rather than to individual buildings or units.
-
E.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a01b3af7b908190b4675c85d32d106c |
completed | May 11, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_6a01b35813c081908e484b2b9ca5dd05 |
completed | May 11, 2026, 10:45 a.m. |
Created at: May 3, 2026, 4:11 p.m.