Triple
T15076368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 National League season |
E380010
|
entity |
| Predicate | LCSResult |
P117222
|
FINISHED |
| Object | Atlanta Braves defeated St. Louis Cardinals 4–3 |
—
|
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: Atlanta Braves defeated St. Louis Cardinals 4–3 | Statement: [1996 National League season, LCSResult, Atlanta Braves defeated St. Louis Cardinals 4–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LCSResult Context triple: [1996 National League season, LCSResult, Atlanta Braves defeated St. Louis Cardinals 4–3]
-
A.
followsMoreLocalAlignmentThan
Indicates that one entity adheres to a more locally focused or fine-grained alignment strategy or standard than another entity.
-
B.
usesMatchLength
Indicates that one entity applies or enforces the same length or duration as that of a corresponding match or matching element.
-
C.
comparisonResult
Indicates the outcome of comparing two entities, typically expressing whether one is less than, equal to, or greater than the other.
-
D.
relatedResult
Indicates that one result is connected or associated with another result, typically as a consequence, counterpart, or supplementary outcome.
-
E.
usesLSA
Indicates that one entity employs Latent Semantic Analysis (LSA) as a method, tool, or underlying technique in relation to another entity or data.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fb60448190b454386dd762644d |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:02 a.m.