Triple
T35290371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SV Kwakel |
E1019203
|
entity |
| Predicate | has competition level |
P5077
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [SV Kwakel, has competition level, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has competition level Context triple: [SV Kwakel, has competition level, regional]
-
A.
involvesCompetitionLevel
Indicates that the relationship or action specifies or depends on a particular degree or intensity of competition involved.
-
B.
competesAtLevel
Indicates that one entity participates in competition at a specified level or tier relative to others.
-
C.
levelOfCompetitionAdministered
Indicates the specific competitive tier or intensity at which an activity, event, or process is formally managed or overseen.
-
D.
levelOfCompetition
chosen
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
-
E.
commonCompetitionLevel
Indicates that two entities participate in competitions that share the same or comparable level of intensity, skill, or ranking.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79012e2e481908c587ff189b3deb3 |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.