Triple
T27143977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punchestown Gold Cup |
E681889
|
entity |
| Predicate | fenceType |
P161895
|
FINISHED |
| Object | steeplechase fences |
—
|
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: steeplechase fences | Statement: [Punchestown Gold Cup, fenceType, steeplechase fences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fenceType Context triple: [Punchestown Gold Cup, fenceType, steeplechase fences]
-
A.
fences
Indicates that one entity constructs, installs, or maintains a fence or barrier around or between entities or areas.
-
B.
numberOfFences
Indicates the quantity of fences associated with or present around a given entity.
-
C.
bordureType
Indicates the specific style or pattern used for the border or edging of an item or area.
-
D.
gateType
Indicates the specific kind or classification of a gate associated with an entity.
-
E.
hasBorderWallOrFence
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f624c3e4bc8190af9a5d9b3c30d117 |
completed | May 2, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 9:10 a.m.