Triple
T6153914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houtribdijk |
E137271
|
entity |
| Predicate | statusOfMarkerwaardProject |
P39444
|
FINISHED |
| Object | cancelled |
—
|
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: cancelled | Statement: [Houtribdijk, statusOfMarkerwaardProject, cancelled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfMarkerwaardProject Context triple: [Houtribdijk, statusOfMarkerwaardProject, cancelled]
-
A.
benchmarkStatus
Indicates the current evaluation state or outcome of a benchmark process applied to an entity or system.
-
B.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
C.
valuationStatus
Indicates the current state or condition of an entity’s assessed value within a valuation process (e.g., pending, active, finalized, or invalid).
-
D.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
E.
worksStatus
chosen
Indicates the current state or condition of an entity’s work or project, such as whether it is planned, in progress, completed, or otherwise categorized.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cffc7bc819092633a9e5f1abe2f |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.