Triple
T31307014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rookie of the Month (MLB) |
E798358
|
entity |
| Predicate | minimumExperience |
P90637
|
FINISHED |
| Object | first MLB 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: first MLB season | Statement: [Rookie of the Month (MLB), minimumExperience, first MLB season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumExperience Context triple: [Rookie of the Month (MLB), minimumExperience, first MLB season]
-
A.
hasExperienceOf
Indicates that one entity has undergone, encountered, or lived through a particular event, situation, or activity associated with another entity.
-
B.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
C.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
D.
typicalExperienceLevel
chosen
Indicates the usual or most common level of experience associated with an entity in a given context.
-
E.
recommendedExperience
Indicates that a certain level or type of prior experience is advised or preferred for engaging in the related activity, role, or item.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 9:14 p.m.