Triple
T4620464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sömmerda |
E100965
|
entity |
| Predicate | hasCentralLocation |
P18768
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sömmerda, hasCentralLocation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralLocation Context triple: [Sömmerda, hasCentralLocation, true]
-
A.
hasCentralAct
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
-
B.
hasCentralLandmark
Indicates that a place or area contains a primary or defining landmark located at or near its center.
-
C.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
D.
centralLocation
chosen
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e560f481908abb1a97b4ff5795 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.