Triple
T2002956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coudenberg |
E43511
|
entity |
| Predicate | afterEventUse |
P1691
|
FINISHED |
| Object | site cleared for construction of the Royal Quarter |
—
|
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: site cleared for construction of the Royal Quarter | Statement: [Coudenberg, afterEventUse, site cleared for construction of the Royal Quarter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterEventUse Context triple: [Coudenberg, afterEventUse, site cleared for construction of the Royal Quarter]
-
A.
endUseEvent
Indicates an event marking the final or terminating use of something by an entity.
-
B.
afterRelease
Indicates that one event, action, or state occurs subsequent to the release of another entity or condition.
-
C.
after
chosen
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
D.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
-
E.
aftermathPolicy
Indicates the policy, rules, or procedures that apply in the aftermath or consequences of a particular event or action.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8820cec8190a945e5daeb8c9df6 |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.