Triple
T35290368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SV Kwakel |
E1019203
|
entity |
| Predicate | operates as |
P140852
|
FINISHED |
| Object | amateur sports association |
—
|
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: amateur sports association | Statement: [SV Kwakel, operates as, amateur sports association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operates as Context triple: [SV Kwakel, operates as, amateur sports association]
-
A.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
-
B.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
C.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
D.
normallyOperatesAs
chosen
Indicates that an entity’s usual or standard mode, role, or state of functioning is as the specified other entity or type.
-
E.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
- 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_6a01295195748190b896d99c3d1f6134 |
completed | May 11, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_6a0128fe96dc8190a73715ab08752dd1 |
completed | May 11, 2026, 12:55 a.m. |
Created at: May 3, 2026, 4:03 p.m.