Triple
T6176795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baseball Ground |
E137838
|
entity |
| Predicate | topDivisionMatchesHosted |
P69259
|
FINISHED |
| Object | First Division |
—
|
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: First Division | Statement: [Baseball Ground, topDivisionMatchesHosted, First Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topDivisionMatchesHosted Context triple: [Baseball Ground, topDivisionMatchesHosted, First Division]
-
A.
topDivision
Indicates that an entity belongs to the highest-level division or tier within a hierarchical structure.
-
B.
topDivisionSanctioning
Indicates that an organization has the authority to sanction or oversee competitions in the highest (top) division of a sport or league.
-
C.
winnerLeagueDivision
Indicates that an entity has won a specific league division in a competitive context.
-
D.
leagueDraws
Indicates that a league competition or season resulted in a specified number of drawn (tied) matches.
-
E.
topDivisionOf
Indicates that one administrative or organizational unit is the highest-level division within the structure of another entity.
- F. None of above. chosen
Provenance (4 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc87bc48190834042d9c41d5b86 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.