Triple
T3610298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talen Energy Stadium |
E76468
|
entity |
| Predicate | hasSupportersSection |
P49935
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Talen Energy Stadium, hasSupportersSection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupportersSection Context triple: [Talen Energy Stadium, hasSupportersSection, yes]
-
A.
hasSupporter
Indicates that one entity supports, endorses, or backs another entity.
-
B.
numberOfSupporters
Indicates the quantity of entities that provide backing, endorsement, or support to a given entity or proposition.
-
C.
hasSupporterGroup
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
-
D.
homeSupportersSectionFor
Indicates that a particular seating section is designated for the home team's supporters at a sporting event or venue.
-
E.
usedBySupporters
Indicates that something is utilized or employed by supporters of a person, group, cause, or entity.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc22b824c8190a85b36185d4957bb |
completed | March 8, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:23 p.m.