Triple
T13311743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger Maris |
E317082
|
entity |
| Predicate | previousRecordSeason |
P109463
|
FINISHED |
| Object | 1927 |
—
|
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: 1927 | Statement: [Roger Maris, previousRecordSeason, 1927]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousRecordSeason Context triple: [Roger Maris, previousRecordSeason, 1927]
-
A.
previousSeason
Indicates that one season directly precedes another in chronological order within the same series or competition.
-
B.
previousRecordHolder
Indicates that one entity was the former holder of a particular record before another entity surpassed or replaced it.
-
C.
previousRecordPoints
Indicates that one record directly precedes and connects to another record in a sequence or history.
-
D.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical context.
-
E.
previousSeasonTiming
Indicates the temporal relationship between an event or state and the timing of the immediately preceding season.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:29 p.m.