Triple
T12244194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SoFi Center |
E291808
|
entity |
| Predicate | technologyUsedFor |
P103689
|
FINISHED |
| Object | enhanced fan experience |
—
|
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: enhanced fan experience | Statement: [SoFi Center, technologyUsedFor, enhanced fan experience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyUsedFor Context triple: [SoFi Center, technologyUsedFor, enhanced fan experience]
-
A.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
B.
technologyUsedBy
Indicates that a particular technology is employed or utilized by a specified entity.
-
C.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
D.
technologyInteractedWith
Indicates that an entity has used, engaged with, or otherwise interacted with a particular technology.
-
E.
platformUsedFor
Indicates that one entity serves as the platform, medium, or environment utilized to perform, host, or support the activities of another 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d91d3654208190a2e0487dfa1d54da |
completed | April 10, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:51 p.m.