Triple
T38463656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Fusion |
E912510
|
entity |
| Predicate | announcedRebrandTo |
P62676
|
FINISHED |
| Object | Seoul Infernal |
—
|
NE NERFINISHED |
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: Seoul Infernal | Statement: [Philadelphia Fusion, announcedRebrandTo, Seoul Infernal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedRebrandTo Context triple: [Philadelphia Fusion, announcedRebrandTo, Seoul Infernal]
-
A.
announcedRebrandingAs
chosen
Indicates that one entity has publicly declared it will change its name, brand, or identity to that of another entity.
-
B.
rebrandedYear
Indicates the year in which an entity changed its brand identity, such as its name, logo, or overall branding.
-
C.
rebrandedWithNetwork
Indicates that an entity has undergone a rebranding that includes or is associated with a specific network or network-related identity.
-
D.
rebrandedReason
Indicates the reason or motivation for which an entity underwent a rebranding.
-
E.
rebrandPeriod
Indicates the time span during which an entity undergoes or is designated for a rebranding.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:31 p.m.