Triple
T32462480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freimann |
E829614
|
entity |
| Predicate | hasEventFacility |
P12416
|
FINISHED |
| Object | large sports and event venues |
—
|
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: large sports and event venues | Statement: [Freimann, hasEventFacility, large sports and event venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventFacility Context triple: [Freimann, hasEventFacility, large sports and event venues]
-
A.
hasEventHostingCapability
Indicates that an entity possesses the ability or resources to host or organize events.
-
B.
hasBackstageFacilities
Indicates that a venue or location provides backstage areas and related facilities for performers or staff.
-
C.
hasFacilityFunction
Indicates that a facility performs, supports, or is designated for a particular function or operational role.
-
D.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
E.
hasVenueProperty
Indicates that a venue possesses or is characterized by a specific property or attribute.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c34f15c88190a2cf86631d80ae35 |
completed | May 3, 2026, 3:38 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:57 a.m.