Triple
T38203056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertz Arena, LLC |
E1009120
|
entity |
| Predicate | associatedVenueNameSponsor |
P15097
|
FINISHED |
| Object | The Hertz Corporation |
E1666352
|
NE 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: The Hertz Corporation | Statement: [Hertz Arena, LLC, associatedVenueNameSponsor, The Hertz Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedVenueNameSponsor Context triple: [Hertz Arena, LLC, associatedVenueNameSponsor, The Hertz Corporation]
-
A.
venueAssociatedWith
Indicates that there is a relevant connection or linkage between an event, activity, or entity and a particular venue or location.
-
B.
sponsorshipName
chosen
Indicates the name or title associated with a sponsorship relationship between entities.
-
C.
venueAlsoKnownAs
Indicates that a venue has an alternative name or alias by which it is also known.
-
D.
hasVenueName
Indicates that an entity has a specific name used to identify the venue where an event or activity takes place.
-
E.
connectsToEventVenue
Indicates that one entity serves as a link or route providing access or connection to an event venue.
- F. None of above.
Provenance (4 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417b4c99c08190b0f5ed6ad59a9581 |
completed | June 28, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.