Triple
T34532412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Reed Rowdies |
E886573
|
entity |
| Predicate | audienceIdentity |
P157946
|
FINISHED |
| Object | 12th Man student body |
—
|
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: 12th Man student body | Statement: [The Reed Rowdies, audienceIdentity, 12th Man student body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceIdentity Context triple: [The Reed Rowdies, audienceIdentity, 12th Man student body]
-
A.
audienceRole
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
-
B.
audienceMember
Indicates that one entity is an audience member who is attending, observing, or listening to a performance, event, or presentation involving the other entity.
-
C.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
-
D.
audienceAccess
Indicates that one entity has permission or ability to access, view, or engage with a particular audience associated with another entity.
-
E.
audienceDescribedAs
chosen
Indicates that an audience is characterized or labeled using a particular description or set of attributes.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fe7d2948190b129fa36963a9b82 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.