Triple
T3384621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strijp |
E71265
|
entity |
| Predicate | redevelopmentStarted |
P11886
|
FINISHED |
| Object | early 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: early 21st century | Statement: [Strijp, redevelopmentStarted, early 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redevelopmentStarted Context triple: [Strijp, redevelopmentStarted, early 21st century]
-
A.
redevelopmentStartDate
Indicates the date on which a redevelopment project or process officially begins.
-
B.
reopenedAfterRedevelopment
Indicates that a place or facility was closed for redevelopment and subsequently opened again once the redevelopment was completed.
-
C.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
D.
developmentStart
chosen
Indicates the point in time or event when the development process of something begins.
-
E.
urbanRedevelopmentArea
Indicates that a location is designated for concentrated urban renewal activities such as redevelopment, revitalization, or land-use transformation.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5ee5e188190912dcea494a12038 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.