Triple
T24722650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q2 Stadium |
E612347
|
entity |
| Predicate | hasNamingRightsPartnerIndustry |
P157202
|
FINISHED |
| Object | financial technology |
—
|
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: financial technology | Statement: [Q2 Stadium, hasNamingRightsPartnerIndustry, financial technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamingRightsPartnerIndustry Context triple: [Q2 Stadium, hasNamingRightsPartnerIndustry, financial technology]
-
A.
hasPartnerInSport
Indicates that one entity has another entity as a partner with whom they jointly participate in a sport or sporting activity.
-
B.
hasNetworkPartner
Indicates that an entity is connected to another entity through a formal or recognized network partnership relationship.
-
C.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
D.
hasPartnershipType
Indicates the specific kind or category of partnership relationship that exists between entities.
-
E.
hasPartnerDesignation
Indicates that one entity is formally designated as a partner of another entity within a specified context or relationship.
- F. None of above. chosen
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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f422add8508190a76e56cfa756eeb8 |
completed | May 1, 2026, 3:49 a.m. |
Created at: April 18, 2026, 3:41 a.m.