Triple
T30814790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 NCAA Division I men's basketball tournament |
E784744
|
entity |
| Predicate | playInLocation |
P170527
|
FINISHED |
| Object | Dayton, Ohio |
—
|
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: Dayton, Ohio | Statement: [2015 NCAA Division I men's basketball tournament, playInLocation, Dayton, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playInLocation Context triple: [2015 NCAA Division I men's basketball tournament, playInLocation, Dayton, Ohio]
-
A.
playIn
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, or venue).
-
B.
locationInPlay
Indicates that an entity is currently situated or active within the defined play area or game environment.
-
C.
playsWithin
Indicates that one entity performs or takes place inside the spatial or temporal bounds of another entity.
-
D.
openingShowLocation
Indicates the place where an opening show or premiere event takes place.
-
E.
play
Indicates that an entity engages in a recreational, performative, or competitive activity, often involving a game, sport, or musical performance, typically with another entity or object.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6906745788190b4876420c801757a |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:43 p.m.