Triple
T5497604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Royals FC |
E144247
|
entity |
| Predicate | fanBaseName |
P65078
|
FINISHED |
| Object | Royals supporters |
—
|
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: Royals supporters | Statement: [Utah Royals FC, fanBaseName, Royals supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanBaseName Context triple: [Utah Royals FC, fanBaseName, Royals supporters]
-
A.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
B.
fanBaseLocation
Indicates the primary geographic area where an individual’s or group’s supporters or fans are predominantly located.
-
C.
fanBaseScope
Indicates the extent or range of people who are considered fans or followers of an entity.
-
D.
fanBaseRelationship
Indicates a relationship in which one party is a fan or supporter of another, typically involving admiration, following, or dedicated interest.
-
E.
fanBaseInteraction
Indicates interactions or engagements occurring between a fan base and the subject, such as communication, feedback, or participatory activities.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f08c2a4819093e772a1497c7ecc |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:32 p.m.