Triple
T23418986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1914 Boston Braves |
E560590
|
entity |
| Predicate | leagueStandingOnJuly4 |
P41792
|
FINISHED |
| Object | last place |
—
|
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: last place | Statement: [1914 Boston Braves, leagueStandingOnJuly4, last place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueStandingOnJuly4 Context triple: [1914 Boston Braves, leagueStandingOnJuly4, last place]
-
A.
leaguePennants
Indicates that a team has won a specified number of league pennants (championship titles) in a particular league.
-
B.
includesAmericanTeams
Indicates that the referenced group, event, or collection contains one or more teams from the United States.
-
C.
federalLeagueStatus
Indicates the status or condition of an entity in relation to its involvement with the Federal League.
-
D.
leagueStandingDescribed
chosen
Indicates that a particular description or statement expresses or explains a team's position or ranking within a league's standings.
-
E.
hasStandings
Indicates that an entity possesses or is associated with a set of rankings, positions, or status levels within a competitive or comparative context.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54489d48190b2b2c29701851765 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:43 p.m.