Triple
T441902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Draft |
E10130
|
entity |
| Predicate | fanEngagement |
P3669
|
FINISHED |
| Object | includes live audiences at draft venues |
—
|
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: includes live audiences at draft venues | Statement: [NFL Draft, fanEngagement, includes live audiences at draft venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanEngagement Context triple: [NFL Draft, fanEngagement, includes live audiences at draft venues]
-
A.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
B.
fanbaseCharacteristic
Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an entity.
-
C.
fanBelief
Indicates that a fan holds a particular belief, opinion, or conviction about someone or something.
-
D.
engagementLevel
chosen
Indicates the degree or intensity of involvement, interest, or participation one entity has in relation to another entity, activity, or context.
-
E.
fanChant
Indicates a relationship where a group of fans collectively chant or vocalize in support of, or in response to, a person, team, or performance.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef42b4008190abed9d79926c7022 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2edde2b9c8190bd20b582eb4c5065 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.