Triple
T18896353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSINet Stadium |
E462217
|
entity |
| Predicate | sponsoredNamePeriodOf |
P13574
|
FINISHED |
| Object | Baltimore Ravens home stadium |
—
|
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: Baltimore Ravens home stadium | Statement: [PSINet Stadium, sponsoredNamePeriodOf, Baltimore Ravens home stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsoredNamePeriodOf Context triple: [PSINet Stadium, sponsoredNamePeriodOf, Baltimore Ravens home stadium]
-
A.
sponsoredNamePeriod
chosen
Indicates a time-bounded period during which an entity’s name is officially sponsored or branded by another party.
-
B.
sponsoredNameHolder
Indicates that one entity holds or uses a name or title under the sponsorship or endorsement of another entity.
-
C.
sponsorshipNameSince
Indicates the date or time from which a particular sponsorship name has been in effect for the associated entity or relationship.
-
D.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
E.
sponsorshipNameAdopted
Indicates that an entity has adopted or taken on a specific sponsorship name as its official or recognized designation.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c47f6c948190918ade08bb88f1fd |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.