Triple
T25205216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Georg Church (Nördlingen) |
E631231
|
entity |
| Predicate | hasTowerName |
P16268
|
FINISHED |
| Object | Daniel |
E891292
|
NE 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: Daniel | Statement: [St. Georg Church (Nördlingen), hasTowerName, Daniel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTowerName Context triple: [St. Georg Church (Nördlingen), hasTowerName, Daniel]
-
A.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
B.
hasTowerPosition
Indicates that an entity occupies or is assigned a specific position or location within a tower.
-
C.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
D.
hasTowerFunction
Indicates that something serves the role or performs the function of a tower in relation to another entity.
-
E.
towerName
chosen
Indicates the specific name assigned to a tower in the relationship.
- F. None of above.
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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a105d0c53848190b301282992d20058 |
completed | May 22, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 12:52 p.m.