Triple
T10300737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sint-Omaars |
E241619
|
entity |
| Predicate | heeftFunctie |
P81043
|
FINISHED |
| Object | regionaleDienstencentrum |
—
|
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: regionaleDienstencentrum | Statement: [Sint-Omaars, heeftFunctie, regionaleDienstencentrum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heeftFunctie Context triple: [Sint-Omaars, heeftFunctie, regionaleDienstencentrum]
-
A.
functie
chosen
Indicates that one entity serves as a function, role, or operational purpose in relation to another entity.
-
B.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
C.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
D.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
E.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2eefe8881908a672c4dca7657ca |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:44 a.m.