Triple
T24444625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manheim |
E616365
|
entity |
| Predicate | hasNewSettlement |
P74360
|
FINISHED |
| Object | Manheim-neu |
—
|
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: Manheim-neu | Statement: [Manheim, hasNewSettlement, Manheim-neu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNewSettlement Context triple: [Manheim, hasNewSettlement, Manheim-neu]
-
A.
hasSubsettlement
chosen
Indicates that one settlement includes another, smaller settlement as a subordinate or component part.
-
B.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
C.
hasPostSettlementEntity
Indicates that one entity is the organization, structure, or body that exists or is established after a settlement, agreement, or resolution involving another entity.
-
D.
hasSettlementOnBanks
Indicates that a settlement is located on or along the banks of a geographic feature such as a river, lake, or coastline.
-
E.
receivedSettlementFrom
Indicates that one party obtained a settlement payment or compensation from another party, typically as the result of a dispute, claim, or legal action.
- 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29852c6908190ab5186cee3693625 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.