Triple
T28441522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margarethe Krupp |
E715722
|
entity |
| Predicate | notable project location |
P42588
|
FINISHED |
| Object | Essen-Margarethenhöhe |
—
|
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: Essen-Margarethenhöhe | Statement: [Margarethe Krupp, notable project location, Essen-Margarethenhöhe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notable project location Context triple: [Margarethe Krupp, notable project location, Essen-Margarethenhöhe]
-
A.
locationOfMajorProject
Indicates the place where a significant or primary project is based, conducted, or implemented.
-
B.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
C.
notableProjectArea
Indicates that an entity has a significant or distinguished project specifically associated with a particular area or domain.
-
D.
hasNotableProjectLocation
chosen
Indicates that an entity has a significant or noteworthy project situated at a particular location.
-
E.
notableProjectFor
Indicates that a particular project is especially significant, prominent, or noteworthy for 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a01185c46f0819089b4a2ad3c3e2f33 |
completed | May 10, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_6a0117e19e008190870663dd45084416 |
completed | May 10, 2026, 11:42 p.m. |
Created at: April 28, 2026, 1:46 a.m.