Triple
T28000278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heudorf (Messkirch) |
E707128
|
entity |
| Predicate | hasNameAddition |
P190331
|
FINISHED |
| Object | (Messkirch) |
—
|
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: (Messkirch) | Statement: [Heudorf (Messkirch), hasNameAddition, (Messkirch)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameAddition Context triple: [Heudorf (Messkirch), hasNameAddition, (Messkirch)]
-
A.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
-
B.
hasGivenNameWith
Indicates that an entity is associated with a specific given (first) name.
-
C.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
D.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
E.
hasGivenNames
Indicates that an entity possesses one or more personal (given) names assigned to it.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: April 27, 2026, 7:56 p.m.