Triple
T30248838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauldorf |
E769136
|
entity |
| Predicate | localSubdivision |
P171071
|
FINISHED |
| Object | Landkreis Sigmaringen |
—
|
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: Landkreis Sigmaringen | Statement: [Sauldorf, localSubdivision, Landkreis Sigmaringen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localSubdivision Context triple: [Sauldorf, localSubdivision, Landkreis Sigmaringen]
-
A.
citySubdivision
Indicates that one administrative or geographic unit is a smaller subdivision contained within a larger city.
-
B.
subdivisionNameLocal
Indicates the locally used or native-language name assigned to a specific administrative or geographic subdivision.
-
C.
collectionSubdivision
Indicates that one collection is a constituent part, section, or subdivision of a larger collection.
-
D.
realmSubdivision
Indicates a hierarchical relationship where one realm is a constituent subdivision or part of a larger realm.
-
E.
isLocatedInSubdivision
Indicates that one place or entity is situated within a more specific administrative or geographic subdivision of another area.
- F. None of above. chosen
Provenance (4 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 7:40 p.m.