Triple
T25631238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luisenstadt |
E642581
|
entity |
| Predicate | currentPartsLocatedIn |
P129663
|
FINISHED |
| Object | Mitte |
—
|
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: Mitte | Statement: [Luisenstadt, currentPartsLocatedIn, Mitte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentPartsLocatedIn Context triple: [Luisenstadt, currentPartsLocatedIn, Mitte]
-
A.
someElementsNowLocatedIn
chosen
Indicates that at least one element of a previously defined set is currently located within a specified place or region.
-
B.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
C.
currentlyLocatedAt
Indicates that an entity’s present or most recent known physical location is at the specified place.
-
D.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 5:18 p.m.