Triple
T10905290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas A&M vs LSU |
E257552
|
entity |
| Predicate | 2018GameCharacteristic |
P92849
|
FINISHED |
| Object | seven overtimes |
—
|
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: seven overtimes | Statement: [Texas A&M vs LSU, 2018GameCharacteristic, seven overtimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2018GameCharacteristic Context triple: [Texas A&M vs LSU, 2018GameCharacteristic, seven overtimes]
-
A.
featuresGame
Indicates that something (such as a platform, service, or collection) includes or presents a particular game as part of its offerings.
-
B.
gameFeatures
chosen
Indicates that a game includes or offers a particular element, characteristic, or functionality.
-
C.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
D.
equipmentCharacteristic
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
E.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770656c288190828e71600bb0acd4 |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.