Triple
T38463406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Fuel |
E912504
|
entity |
| Predicate |
P2866
|
FINISHED | |
| Object | @DallasFuel |
—
|
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: @DallasFuel | Statement: [Dallas Fuel, twitter, @DallasFuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: twitter Context triple: [Dallas Fuel, twitter, @DallasFuel]
-
A.
twitterUsername
Indicates that one entity is the Twitter handle or username associated with another entity.
-
B.
twitterHandle
chosen
Indicates that one entity is the Twitter username or account identifier associated with another entity.
-
C.
socialMediaTrend
Indicates that something is currently popular, widely discussed, or rapidly spreading in visibility and engagement on social media platforms.
-
D.
screenName
Indicates the display or handle name associated with an entity, typically used as its visible identifier in user interfaces or social platforms.
-
E.
socialMedia
Indicates a relationship where one entity uses, is associated with, or interacts through social networking or content-sharing platforms with another entity.
- 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_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.