Triple
T28865083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaping Gill |
E728975
|
entity |
| Predicate | publicWinchOccurs |
P192488
|
FINISHED |
| Object | spring bank holiday |
—
|
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: spring bank holiday | Statement: [Gaping Gill, publicWinchOccurs, spring bank holiday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicWinchOccurs Context triple: [Gaping Gill, publicWinchOccurs, spring bank holiday]
-
A.
winnerThrows
Indicates that the entity identified as the winner performs or executes a throw action toward or involving another entity.
-
B.
classWins
Indicates that a particular class has achieved victory or success in a competitive context.
-
C.
winnerWins
Indicates that the entity identified as the winner achieves victory over another entity or in a specified competition or event.
-
D.
winnerRight
Indicates that the referenced entity is the winner on the right side or right position in a competitive or comparative context.
-
E.
winsFor
Indicates that one entity achieves victory or success on behalf of, or in favor of, another 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69fd0d0aebac8190868a7714ddb4f1fd |
completed | May 7, 2026, 10:07 p.m. |
Created at: April 28, 2026, 6:48 a.m.