Triple
T37043460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himberg |
E916843
|
entity |
| Predicate | localityOf |
P188496
|
FINISHED |
| Object | Aegidienberg |
—
|
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: Aegidienberg | Statement: [Himberg, localityOf, Aegidienberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localityOf Context triple: [Himberg, localityOf, Aegidienberg]
-
A.
localityCondition
Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
-
B.
subjectLocality
Indicates that one entity serves as the geographic or jurisdictional area associated with, relevant to, or governing the other entity.
-
C.
typeLocality
Indicates the specific geographic location where a specimen or taxon was originally found and formally described.
-
D.
originLocality
Indicates the specific locality or place where an entity (typically a specimen or item) originally came from or was collected.
-
E.
coversLocality
Indicates that one entity spatially includes or encompasses the area or extent of a specified locality.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:14 p.m.