Triple
T32504901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rae’s Creek |
E830762
|
entity |
| Predicate | guardsGreenOf |
P174998
|
FINISHED |
| Object | 12th hole at Augusta National Golf Club |
—
|
NE NERFINISHED |
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: 12th hole at Augusta National Golf Club | Statement: [Rae’s Creek, guardsGreenOf, 12th hole at Augusta National Golf Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardsGreenOf Context triple: [Rae’s Creek, guardsGreenOf, 12th hole at Augusta National Golf Club]
-
A.
guard
Indicates that one entity protects, watches over, or defends another entity or resource from harm, intrusion, or unauthorized access.
-
B.
typicalGuard
Indicates that an entity commonly or characteristically serves in a guarding or protective role relative to another entity or context.
-
C.
greensGrass
Indicates that an entity (typically an animal) feeds on or consumes grass as its primary or regular food source.
-
D.
shieldColor
Indicates the color attribute assigned to a shield in the relationship.
-
E.
guardType
Indicates the specific kind or category of guarding role or protection associated with an entity.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1 a.m.