Triple
T405190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National League East |
E9367
|
entity |
| Predicate | usesScheduleFormat |
P11168
|
FINISHED |
| Object | Major League Baseball regular season schedule |
—
|
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 schedule | Statement: [National League East, usesScheduleFormat, Major League Baseball regular season schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScheduleFormat Context triple: [National League East, usesScheduleFormat, Major League Baseball regular season schedule]
-
A.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
C.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
-
D.
meetsDuring
Indicates that one entity encounters or comes together with another while a specified event or time interval is in progress.
-
E.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca37fe881909802126952dfdd59 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.