Triple
T35290369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SV Kwakel |
E1019203
|
entity |
| Predicate | serves community |
P119302
|
FINISHED |
| Object | De Kwakel |
—
|
NE NERFINISHED |
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: De Kwakel | Statement: [SV Kwakel, serves community, De Kwakel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serves community Context triple: [SV Kwakel, serves community, De Kwakel]
-
A.
servesCommunityDescribedAs
Indicates that an entity provides services or support to a community characterized or described in a particular way.
-
B.
servesCommunityFunction
Indicates that something performs a role or provides a service that benefits or supports a community as a whole.
-
C.
servesNearbyCommunities
chosen
Indicates that an entity provides services or support to communities located in its surrounding area.
-
D.
servesCommunitiesAlong
Indicates that something provides services or support to the communities located along a particular route, corridor, or area.
-
E.
sharesCommunityServices
Indicates that two or more entities use, provide, or are served by the same community-based services or facilities.
- 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_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
Created at: May 3, 2026, 4:03 p.m.