Triple
T24501139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soeters Van Eldonk architecten |
E617934
|
entity |
| Predicate | knownForProjectType |
P6242
|
FINISHED |
| Object | harbor area redevelopments |
—
|
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: harbor area redevelopments | Statement: [Soeters Van Eldonk architecten, knownForProjectType, harbor area redevelopments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForProjectType Context triple: [Soeters Van Eldonk architecten, knownForProjectType, harbor area redevelopments]
-
A.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
B.
eligibleProjectType
Indicates that a project belongs to a category or type that qualifies it for a specific program, process, or benefit.
-
C.
notableProjectType
chosen
Indicates the type or category of a project for which an entity is particularly well-known or notable.
-
D.
supportsProjectType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
-
E.
typicalProjectTypes
Indicates the kinds or categories of projects that are most commonly or characteristically associated with a given entity.
- 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.