Triple
T17171829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modern Baseball Committee |
E416752
|
entity |
| Predicate | hasCandidateType |
P16808
|
FINISHED |
| Object | post-playing career candidates |
—
|
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: post-playing career candidates | Statement: [Modern Baseball Committee, hasCandidateType, post-playing career candidates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCandidateType Context triple: [Modern Baseball Committee, hasCandidateType, post-playing career candidates]
-
A.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
C.
hasCapType
Indicates that an entity possesses or is characterized by a specific type of cap or cap-like feature.
-
D.
hasCurrentType
Indicates that an entity currently possesses or is classified under a specific type or category, as opposed to past or potential types.
-
E.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0ac22481909e992bb3a6ba36ad |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.