Triple
T21744656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scope Complex |
E536754
|
entity |
| Predicate | containsVenueType |
P130916
|
FINISHED |
| Object | indoor arena |
—
|
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 arena | Statement: [Scope Complex, containsVenueType, indoor arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsVenueType Context triple: [Scope Complex, containsVenueType, indoor arena]
-
A.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
B.
hasVenueComponentType
chosen
Indicates that a venue is associated with a specific type of component or functional part it contains or comprises.
-
C.
locatedInVenueType
Indicates that an entity is situated within or associated with a venue of a specific type (e.g., stadium, theater, restaurant).
-
D.
isVenueWithin
Indicates that one venue is geographically located inside the boundaries or area of another place or region.
-
E.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a75352c8190bcd46759562ee251 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.