Triple
T6001311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luv Ya Blue |
E133601
|
entity |
| Predicate | fanDemographic |
P6226
|
FINISHED |
| Object | Houston-area football fans |
—
|
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: Houston-area football fans | Statement: [Luv Ya Blue, fanDemographic, Houston-area football fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanDemographic Context triple: [Luv Ya Blue, fanDemographic, Houston-area football fans]
-
A.
fanbaseCharacteristic
chosen
Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an entity.
-
B.
fanInterestLevel
Indicates the degree or intensity of enthusiasm or interest that a fan has toward a particular subject, such as a person, team, or work.
-
C.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
D.
hasDemographic
Indicates that an entity is associated with or characterized by a particular demographic group or attribute.
-
E.
fanTerm
Indicates that one entity is a term, label, or expression used by fans to refer to or describe 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee7c0e08190a6e78969448b070a |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.