Triple
T16996592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SevenVenues |
E412330
|
entity |
| Predicate | ownedFacilitiesAre |
P12416
|
FINISHED |
| Object | publicly owned |
—
|
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: publicly owned | Statement: [SevenVenues, ownedFacilitiesAre, publicly owned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedFacilitiesAre Context triple: [SevenVenues, ownedFacilitiesAre, publicly owned]
-
A.
ownsFacilityOn
Indicates that one entity possesses ownership or control over a facility located on or associated with another entity (such as a site, property, or area).
-
B.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
C.
usesFacilityFor
Indicates that an entity makes use of a particular facility to carry out a specific purpose, activity, or function.
-
D.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
E.
legacyFacilityOf
Indicates that one facility is an older, predecessor, or superseded version of another facility within the same organizational or operational context.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d2885f888190ab1406f55a91bf93 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.