Triple
T24021352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbasol Championship |
E594829
|
entity |
| Predicate | isAlternateFieldEvent |
P154891
|
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: [Barbasol Championship, isAlternateFieldEvent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAlternateFieldEvent Context triple: [Barbasol Championship, isAlternateFieldEvent, true]
-
A.
hasAlternateKey
Indicates that an entity is associated with an additional, non-primary identifier that can uniquely distinguish it as an alternative to the primary key.
-
B.
isAlternating
Indicates that a sequence or pattern switches back and forth between two (or more) distinct states, values, or conditions in a regular, repeating manner.
-
C.
inSameFieldAs
Indicates that two entities work, study, or specialize within the same professional or academic field.
-
D.
isMajorFieldWithin
Indicates that one academic or professional major field is contained within or is a specialization of a broader field.
-
E.
hasAlternateCut
Indicates that an entity has an alternative edited version or cut, distinct from its primary or original form.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5aaf8588190b266557d573504b8 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:47 p.m.