Triple
T18579969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frenchgate Shopping Centre |
E454083
|
entity |
| Predicate | hasIndoorOutdoor |
P8552
|
FINISHED |
| Object | indoor |
—
|
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: indoor | Statement: [Frenchgate Shopping Centre, hasIndoorOutdoor, indoor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndoorOutdoor Context triple: [Frenchgate Shopping Centre, hasIndoorOutdoor, indoor]
-
A.
indoorOrOutdoor
chosen
Indicates whether an activity, event, or entity occurs inside a building (indoors) or outside in open air (outdoors).
-
B.
hasIndoorType
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
-
C.
isIndoorOutdoorHybrid
Indicates that something functions as both an indoor and outdoor variant or environment, combining characteristics of each.
-
D.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
E.
hasIndoorArea
Indicates that an entity possesses or includes an area or space that is located indoors or within a building.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543cf33288190bc2cd6b7befde944 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.