Triple
T37856119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1988 NCAA Division I-A football national championship |
E944194
|
entity |
| Predicate | bowlCity |
P189282
|
FINISHED |
| Object | Tempe, Arizona |
—
|
NE NERFINISHED |
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: Tempe, Arizona | Statement: [1988 NCAA Division I-A football national championship, bowlCity, Tempe, Arizona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bowlCity Context triple: [1988 NCAA Division I-A football national championship, bowlCity, Tempe, Arizona]
-
A.
bowlSystem
Indicates a relationship where one entity functions as or belongs to a bowling-related system, setup, or arrangement involving bowls or bowling equipment.
-
B.
bowlAccess
Indicates that one entity has the ability or permission to access or use a particular bowl.
-
C.
bowls
Indicates that an entity performs the action of bowling, typically rolling a ball toward a target such as pins or a wicket.
-
D.
bowlOutcome
Indicates the result or consequence of a bowling action or event for the involved entities.
-
E.
includesBowl
Indicates that something contains or has a bowl as one of its components or elements.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbae3fc508190adff3d7abbf107a4 |
completed | May 6, 2026, 10:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.