Triple
T38535593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina vs. Michigan |
E923488
|
entity |
| Predicate | finalScoreMichigan |
P2625
|
FINISHED |
| Object | 71 |
—
|
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: 71 | Statement: [North Carolina vs. Michigan, finalScoreMichigan, 71]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreMichigan Context triple: [North Carolina vs. Michigan, finalScoreMichigan, 71]
-
A.
Michigan StateScore
Indicates that a specified score is associated with Michigan State in a particular game or event.
-
B.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
halftimeLeadMarginMichigan
Indicates the point-margin by which Michigan is leading or trailing at halftime of a game.
-
D.
michiganStateOutcomeInTournament
Indicates the specific result or performance outcome that Michigan State achieved in a particular tournament.
-
E.
overallRecordAtMichigan
Indicates the overall win-loss (and possibly tie) record that an entity has achieved while at Michigan.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: May 3, 2026, 4:32 p.m.