Triple
T27016771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wemmel |
E680554
|
entity |
| Predicate | hasProtectedBuilding |
P98926
|
FINISHED |
| Object | Wemmel Castle |
—
|
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: Wemmel Castle | Statement: [Wemmel, hasProtectedBuilding, Wemmel Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectedBuilding Context triple: [Wemmel, hasProtectedBuilding, Wemmel Castle]
-
A.
hasProtectedArea
Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
-
B.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
C.
hasProtectedAreaAccess
Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
-
D.
hasBuildingUnderCare
chosen
Indicates that an entity is responsible for the maintenance, management, or oversight of a particular building.
-
E.
isProtectedAreaOf
Indicates that a designated protected area (such as a park or reserve) is established to conserve and manage a specific geographic region or natural 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 27, 2026, 7:06 a.m.