Triple
T4571338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hofvijver |
E123035
|
entity |
| Predicate | waterBodyOrigin |
P12617
|
FINISHED |
| Object | artificial |
—
|
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: artificial | Statement: [Hofvijver, waterBodyOrigin, artificial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyOrigin Context triple: [Hofvijver, waterBodyOrigin, artificial]
-
A.
waterOrigin
chosen
Indicates the source or starting location from which the water originates or is supplied.
-
B.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
C.
waterbodyID
Indicates a unique identifier that links an entity to a specific body of water.
-
D.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
E.
hasHydronymOrigin
Indicates that something derives its name from a body of water or hydrological feature.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c5afa48190bb8505e2cc16e89f |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.