Triple
T49365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1903 World Series |
E970
|
entity |
| Predicate | seriesResult |
P1421
|
FINISHED |
| Object | Boston Americans 5–3 Pittsburgh Pirates |
—
|
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: Boston Americans 5–3 Pittsburgh Pirates | Statement: [1903 World Series, seriesResult, Boston Americans 5–3 Pittsburgh Pirates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesResult Context triple: [1903 World Series, seriesResult, Boston Americans 5–3 Pittsburgh Pirates]
-
A.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
B.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
C.
historicalOutcome
chosen
Indicates the result or consequence that an event, action, or situation produced in a historical context.
-
D.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
E.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abfa7bc8190932c137a823efcb6 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.