Triple
T6106652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan Golf Tour |
E136132
|
entity |
| Predicate | providesExemptionsTo |
P68180
|
FINISHED |
| Object | major championships |
—
|
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 championships | Statement: [Japan Golf Tour, providesExemptionsTo, major championships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesExemptionsTo Context triple: [Japan Golf Tour, providesExemptionsTo, major championships]
-
A.
exemptedFrom
Indicates that an entity is not subject to, or is formally released from, a rule, obligation, requirement, or liability that would otherwise apply.
-
B.
exemptionType
Indicates the specific category or kind of exemption that applies in a given context.
-
C.
eliminatesPersonalExemptions
Indicates that a policy or action removes previously available personal tax exemptions for individuals.
-
D.
exemptedJurisdiction
Indicates that one jurisdiction is officially excluded from the application, scope, or requirements that apply to other jurisdictions.
-
E.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b806bd48190b6f020af3391adb8 |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:13 p.m.