Triple
T32959292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oostelijke Ourthe |
E843187
|
entity |
| Predicate | heeftKenmerk |
P128001
|
FINISHED |
| Object | natuurlijk waterlichaam |
—
|
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: natuurlijk waterlichaam | Statement: [Oostelijke Ourthe, heeftKenmerk, natuurlijk waterlichaam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heeftKenmerk Context triple: [Oostelijke Ourthe, heeftKenmerk, natuurlijk waterlichaam]
-
A.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
-
B.
entityCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
C.
subjectHasCharacteristic
Indicates that a subject possesses, exhibits, or is defined by a particular characteristic or attribute.
-
D.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
E.
valueCharacteristic
Indicates that one entity serves as a value or specific quantitative/qualitative measure that characterizes or describes another entity.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:21 a.m.