Triple
T30738488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 NCAA Division I women's basketball tournament |
E782627
|
entity |
| Predicate | atLargeBidCount |
P170082
|
FINISHED |
| Object | 34 |
—
|
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: 34 | Statement: [1995 NCAA Division I women's basketball tournament, atLargeBidCount, 34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: atLargeBidCount Context triple: [1995 NCAA Division I women's basketball tournament, atLargeBidCount, 34]
-
A.
atLarge
Indicates that an individual is currently not in custody and remains free despite being sought by authorities.
-
B.
numberOfAutomaticBids
Indicates the total count of automatic bids associated with or placed in a given bidding context.
-
C.
notableBid
Indicates that an entity has made a bid or offer that is considered significant, prominent, or otherwise noteworthy in its context.
-
D.
biddingRival
Indicates a competitive relationship where two or more parties are actively bidding against each other for the same opportunity, resource, or contract.
-
E.
bidsFrom
Indicates that one entity has submitted or placed a bid originating from it toward another entity or item.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68ee9435081908efcb423c2eaf1ab |
completed | May 2, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68848ad348190a2fb6e841dcfdb7d |
completed | May 2, 2026, 11:27 p.m. |
Created at: April 29, 2026, 8:37 p.m.