Triple
T23712748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 NCAA Division I men's basketball championship |
E585910
|
entity |
| Predicate | pointMargin |
P66013
|
FINISHED |
| Object | 13 points |
—
|
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: 13 points | Statement: [1981 NCAA Division I men's basketball championship, pointMargin, 13 points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointMargin Context triple: [1981 NCAA Division I men's basketball championship, pointMargin, 13 points]
-
A.
leafMargin
Indicates the type or pattern of the edge or border of a leaf (e.g., smooth, serrated, lobed).
-
B.
margining
Indicates the process of posting, adjusting, or settling collateral (margin) between parties to secure obligations in a financial transaction or trading relationship.
-
C.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
D.
marginOf
chosen
Indicates the difference or buffer between two related quantities, values, or boundaries, often expressing how much one exceeds or falls short of another.
-
E.
gapBetween
Indicates the spatial or temporal distance or separation that exists between two entities.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b7784cd08190a442dd41d56b92b1 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:54 p.m.