Triple
T8004777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 12th Man (Texas A&M) |
E186336
|
entity |
| Predicate | fanRole |
P6226
|
FINISHED |
| Object | provide loud support and intimidation for opponents |
—
|
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: provide loud support and intimidation for opponents | Statement: [12th Man (Texas A&M), fanRole, provide loud support and intimidation for opponents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanRole Context triple: [12th Man (Texas A&M), fanRole, provide loud support and intimidation for opponents]
-
A.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
B.
fanInvolved
Indicates that a fan actively participates in or is directly involved with a particular event, activity, or interaction.
-
C.
fanDestination
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
-
D.
fanTerm
Indicates that one entity is a term, label, or expression used by fans to refer to or describe another entity.
-
E.
fanbaseCharacteristic
chosen
Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf5fb588190ada4ec7d8087619c |
completed | March 31, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:18 p.m.