Triple
T1188293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masters Tournament |
E25297
|
entity |
| Predicate | cutRule |
P26145
|
FINISHED |
| Object | top 50 and ties after 36 holes |
—
|
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: top 50 and ties after 36 holes | Statement: [Masters Tournament, cutRule, top 50 and ties after 36 holes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cutRule Context triple: [Masters Tournament, cutRule, top 50 and ties after 36 holes]
-
A.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
B.
displayRule
Indicates the rule or condition that determines how something should be visually presented or displayed.
-
C.
setsRulesFor
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
-
D.
divisionLine
Indicates a boundary or separating line that divides one area, group, or portion from another.
-
E.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd568cf481908d10cf19a3ce28f3 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd0ab5f88190bb583fc63b4cc150 |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:45 p.m.