Triple
T34824341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadsbuitengracht |
E1003873
|
entity |
| Predicate | wasPartlyRestoredAsWater |
P38760
|
FINISHED |
| Object | 21st century |
—
|
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: 21st century | Statement: [Stadsbuitengracht, wasPartlyRestoredAsWater, 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPartlyRestoredAsWater Context triple: [Stadsbuitengracht, wasPartlyRestoredAsWater, 21st century]
-
A.
restoredInPart
Indicates that something has been brought back to a previous or improved state, but only partially rather than fully.
-
B.
waterSourceRestored
Indicates that a previously unavailable or degraded water source has been returned to a functional and usable condition.
-
C.
recoveredFromLake
Indicates that something was retrieved or taken out from a lake.
-
D.
partiallyRestored
chosen
Indicates that an entity has been brought back toward a previous or original state, but the restoration is incomplete or only partially achieved.
-
E.
laterRestored
Indicates that something previously altered, damaged, or removed was subsequently brought back to its earlier state or condition.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.