Triple
T36917063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Tech vs Michigan State |
E913071
|
entity |
| Predicate | MichiganStateSeed |
P186744
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Texas Tech vs Michigan State, MichiganStateSeed, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MichiganStateSeed Context triple: [Texas Tech vs Michigan State, MichiganStateSeed, 2]
-
A.
MississippiStateSeed
Indicates that an entity is designated as a seed (i.e., a ranked or qualifying position) specifically within the context of Mississippi State.
-
B.
marylandSeed
Indicates a seeding or ranking assignment that is specific to Maryland within a competitive or organizational context.
-
C.
Michigan StateScore
Indicates that a specified score is associated with Michigan State in a particular game or event.
-
D.
indianaSeed
Indicates a seeding or ranking position assigned within the context of Indiana (e.g., an Indiana-based tournament, system, or classification).
-
E.
Michigan StateConference
Indicates that a college or university’s athletic programs compete in the same athletic conference as Michigan State University.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.