Triple
T36894016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shrine to Jobu |
E911837
|
entity |
| Predicate | settingTimeInWork |
P32393
|
FINISHED |
| Object | Cleveland Indians season |
—
|
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: Cleveland Indians season | Statement: [shrine to Jobu, settingTimeInWork, Cleveland Indians season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingTimeInWork Context triple: [shrine to Jobu, settingTimeInWork, Cleveland Indians season]
-
A.
workSettingPeriod
chosen
Indicates the time period during which a particular work setting or employment context is in effect.
-
B.
workSetting
Indicates the environment, context, or conditions in which the work or activity is carried out.
-
C.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
D.
settingStateOfWork
Indicates that an entity is assigning or changing the current state or status of a work item or task.
-
E.
setAfterWork
Indicates that one event, state, or action is scheduled or configured to occur after the completion of work or working hours.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:13 p.m.