Triple
T17701078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tal’s Hill |
E441300
|
entity |
| Predicate | usedDuringLeague |
P4341
|
FINISHED |
| Object | Major League Baseball regular season games |
—
|
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: Major League Baseball regular season games | Statement: [Tal’s Hill, usedDuringLeague, Major League Baseball regular season games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDuringLeague Context triple: [Tal’s Hill, usedDuringLeague, Major League Baseball regular season games]
-
A.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
B.
usedDuringTeam
Indicates that something is utilized or applied in the context of a team activity, process, or collaboration.
-
C.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
usedInCompetition
Indicates that something is employed or utilized as part of a competition or contest.
-
E.
usedForLevelOfPlay
Indicates that something is intended or suitable for a particular level or standard of play.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715ae1fc81908438a1bba970c6ec |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:04 a.m.