Triple
T13781431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calendar Grand Slam |
E331138
|
entity |
| Predicate | appliesToProfessionalEra |
P36703
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Calendar Grand Slam, appliesToProfessionalEra, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToProfessionalEra Context triple: [Calendar Grand Slam, appliesToProfessionalEra, true]
-
A.
professionalEra
Indicates the time period during which an entity was active in a professional capacity within a given field or role.
-
B.
appliesToEra
chosen
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
C.
hasProfessionalApplication
Indicates that something is used or applied within a professional, occupational, or work-related context.
-
D.
hasProfessionalCore
Indicates that an entity possesses a central set of professional skills, knowledge, or competencies that define its primary professional function or expertise.
-
E.
grantsProfessionalLicenseEligibility
Indicates that one entity confers eligibility upon another entity to obtain a professional license.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02460a688190a27874f8d35819c7 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe98b5bc8190967907ec64d0317d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:11 p.m.