Triple
T13275626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wimbledon men's wheelchair singles 2016 |
E316180
|
entity |
| Predicate | hasEventScope |
P397
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [Wimbledon men's wheelchair singles 2016, hasEventScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventScope Context triple: [Wimbledon men's wheelchair singles 2016, hasEventScope, international]
-
A.
hasEventSpace
Indicates that an entity provides or includes a designated space intended for hosting events.
-
B.
hasScope
chosen
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
C.
hasBroadcastScope
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
-
D.
hasSubEvent
Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
-
E.
hasDeterminingEvent
Indicates that one event or occurrence serves as the decisive cause, condition, or basis that determines another situation, outcome, or state.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.