Triple
T36177857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hühnermarkt |
E1046624
|
entity |
| Predicate | redevelopedAsPartOf |
P50758
|
FINISHED |
| Object | Dom-Römer project |
—
|
NE NERFINISHED |
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: Dom-Römer project | Statement: [Hühnermarkt, redevelopedAsPartOf, Dom-Römer project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redevelopedAsPartOf Context triple: [Hühnermarkt, redevelopedAsPartOf, Dom-Römer project]
-
A.
redevelopedAfter
Indicates that one entity was redeveloped at a later time than, and as a subsequent phase or replacement to, another entity.
-
B.
partOfRedevelopmentOf
chosen
Indicates that something is a component or phase within a larger redevelopment project or process.
-
C.
developedAsPartOf
Indicates that something was created, produced, or evolved as a component or subset of a larger project, system, or initiative.
-
D.
redevelopmentFrom
Indicates that one entity is created or transformed as a result of redeveloping or repurposing another pre-existing entity.
-
E.
redevelopmentFor
Indicates a relationship where one entity is intended, designated, or used for the redevelopment of another 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.