Triple
T33880516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacArthur Bowl |
E868469
|
entity |
| Predicate | isTiedToPollEra |
P178386
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MacArthur Bowl, isTiedToPollEra, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTiedToPollEra Context triple: [MacArthur Bowl, isTiedToPollEra, true]
-
A.
isTiedToBCSEra
Indicates that something has a connection or association with the BCS (Bowl Championship Series) era, typically in terms of time period, rules, or context.
-
B.
isBsideOfEra
Indicates that one entity is the B-side counterpart associated with a particular era of another entity (such as a primary release or period).
-
C.
appliesToElectionYear
Indicates that something is relevant, valid, or in effect specifically for a given election year.
-
D.
appliesFromElectionCycle
Indicates that a rule, condition, or status becomes applicable starting from a specified election cycle and continuing thereafter.
-
E.
hasHistoricalTieTo
Indicates a relationship where one entity is historically connected or linked to another through past events, associations, or influences.
- F. None of above. chosen
Provenance (4 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:48 a.m.