Triple
T22743203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch Madness |
E562471
|
entity |
| Predicate | fanActivitiesInclude |
P74196
|
FINISHED |
| Object | pep rallies |
—
|
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: pep rallies | Statement: [Arch Madness, fanActivitiesInclude, pep rallies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanActivitiesInclude Context triple: [Arch Madness, fanActivitiesInclude, pep rallies]
-
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.
fandomActivity
chosen
Indicates participation in or engagement with fan-related activities centered around a particular work, person, or franchise.
-
D.
fanOwned
Indicates that the entity is owned or controlled by fans, typically through collective or community-based ownership rather than traditional private or corporate ownership.
-
E.
fanAttraction
Indicates a relationship where one entity is strongly drawn to, admires, or is devoted to another as a fan.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17974c3208190ae1d6b05639cc942 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:23 p.m.