Triple
T22345110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Askernish Golf Club |
E552370
|
entity |
| Predicate | hasPlayingConditions |
P1255
|
FINISHED |
| Object | wind-affected |
—
|
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: wind-affected | Statement: [Askernish Golf Club, hasPlayingConditions, wind-affected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayingConditions Context triple: [Askernish Golf Club, hasPlayingConditions, wind-affected]
-
A.
hasCondition
chosen
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
B.
hasNumberOfConditions
Indicates that an entity is associated with a specific count of conditions it has or is subject to.
-
C.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
-
D.
hasProtagonistCondition
Indicates that the main character in a narrative has a particular condition, state, or affliction.
-
E.
hasOpeningCondition
Indicates that a relationship or action is subject to a specific initial condition that must be met before it can begin or take effect.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157975db481909db65ff4d8505bbd |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.