Triple
T4122215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arena Football League |
E92638
|
entity |
| Predicate | hasFanExperienceFeature |
P29388
|
FINISHED |
| Object | proximity of fans to field |
—
|
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: proximity of fans to field | Statement: [Arena Football League, hasFanExperienceFeature, proximity of fans to field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanExperienceFeature Context triple: [Arena Football League, hasFanExperienceFeature, proximity of fans to field]
-
A.
fanExperienceFeature
chosen
Indicates a feature or aspect specifically designed to shape, enhance, or characterize a fan’s overall experience.
-
B.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
-
C.
hasFanActivity
Indicates that an entity is associated with actions, behaviors, or engagement carried out by fans in relation to it.
-
D.
hasFanPerception
Indicates that an entity is perceived, interpreted, or regarded in a particular way by its fans or fan community.
-
E.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.