Triple
T402404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Cardinals (NFL) |
E9312
|
entity |
| Predicate | franchiseFoundedYear |
P4025
|
FINISHED |
| Object | 1898 |
—
|
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: 1898 | Statement: [St. Louis Cardinals (NFL), franchiseFoundedYear, 1898]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseFoundedYear Context triple: [St. Louis Cardinals (NFL), franchiseFoundedYear, 1898]
-
A.
foundedAt
chosen
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
B.
franchiseOf
Indicates that one entity operates as a franchise belonging to or licensed by another entity.
-
C.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
D.
foundedInYearApprox
Indicates that an entity was established or came into existence around an approximate year, rather than on a precisely known date.
-
E.
franchiseEventuallyBecame
Indicates that one franchise transformed into, was succeeded by, or ultimately came to be identified as another franchise over time.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca0e2048190a7bf360257965e56 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96ee4ec8190a5c0e3f491d3963d |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.