Triple
T1113989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 National League pennant |
E11054
|
entity |
| Predicate | conferredTitle |
P3622
|
FINISHED |
| Object | National League champion |
—
|
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: National League champion | Statement: [2009 National League pennant, conferredTitle, National League champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferredTitle Context triple: [2009 National League pennant, conferredTitle, National League champion]
-
A.
confersTitle
chosen
Indicates that one entity grants or bestows an official title or designation upon another entity.
-
B.
conferredIn
Indicates that something (such as a degree, title, or honor) was formally granted or awarded within a particular context, event, or institution.
-
C.
creditedTitle
Indicates that a particular title or role is formally attributed to an entity as a credit.
-
D.
conferredOn
Indicates that something (such as an honor, title, degree, or benefit) has been formally granted or bestowed upon a particular entity.
-
E.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.