Triple
T12027801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NLE |
E286322
|
entity |
| Predicate | usesInStandings |
P94650
|
FINISHED |
| Object | MLB standings |
—
|
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: MLB standings | Statement: [NLE, usesInStandings, MLB standings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInStandings Context triple: [NLE, usesInStandings, MLB standings]
-
A.
usesInStandingsTables
chosen
Indicates that something is employed or applied within standings tables, such as rankings or league tables, to represent or organize comparative positions.
-
B.
hasStandings
Indicates that an entity possesses or is associated with a set of rankings, positions, or status levels within a competitive or comparative context.
-
C.
usesRegularSeasonStandingsFor
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
D.
hadStandingsPublishedIn
Indicates that the standings or rankings associated with an entity were published in a particular source, venue, or medium.
-
E.
standingsCriteria
Indicates the rules or factors used to determine the relative ranking or position of entities in a standings or leaderboard.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.