Triple
T35058132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2012 Venlo Floriade |
E1011520
|
entity |
| Predicate | siteReuse |
P13075
|
FINISHED |
| Object | business park |
—
|
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: business park | Statement: [2012 Venlo Floriade, siteReuse, business park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteReuse Context triple: [2012 Venlo Floriade, siteReuse, business park]
-
A.
reusesSiteOf
Indicates that one entity occupies or uses the same site or location that was previously used by another entity.
-
B.
originalSiteUse
Indicates the historical or initial functional use or purpose assigned to a particular site before any subsequent changes or developments.
-
C.
isReuseOf
Indicates that one entity is derived from, or created by reusing, the content, structure, or components of another entity.
-
D.
relaunchSite
Indicates restarting or reintroducing a previously existing website, typically after updates, redesign, or a period of inactivity.
-
E.
siteRedevelopedAs
chosen
Indicates that a site has been transformed, rebuilt, or repurposed into a new form, function, or development.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f785d2ed3c8190b3444fbc6e527cb3 |
completed | May 3, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.