Triple
T1602317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phones 4u Arena |
E34420
|
entity |
| Predicate | sponsorshipPeriod |
P13574
|
FINISHED |
| Object | 2013–2015 |
—
|
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: 2013–2015 | Statement: [Phones 4u Arena, sponsorshipPeriod, 2013–2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorshipPeriod Context triple: [Phones 4u Arena, sponsorshipPeriod, 2013–2015]
-
A.
sponsoredNamePeriod
chosen
Indicates a time-bounded period during which an entity’s name is officially sponsored or branded by another party.
-
B.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
C.
serviceEntryPeriod
Indicates the span of time during which a service is active, valid, or in effect for the related entities.
-
D.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
E.
sponsorshipDealStart
Indicates the point in time when a sponsorship agreement between parties officially begins.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.