Triple
T35221520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Martin's Church (Landshut) |
E1016968
|
entity |
| Predicate | towerRanking |
P31595
|
FINISHED |
| Object | one of the tallest brick church towers in the world |
—
|
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: one of the tallest brick church towers in the world | Statement: [St. Martin's Church (Landshut), towerRanking, one of the tallest brick church towers in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerRanking Context triple: [St. Martin's Church (Landshut), towerRanking, one of the tallest brick church towers in the world]
-
A.
towerCount
Indicates the number of towers associated with or present in a given entity or context.
-
B.
towerName
Indicates the specific name assigned to a tower in the relationship.
-
C.
rankAmongTallestBuildings
chosen
Indicates that one building is among the tallest buildings within a specified group, area, or category.
-
D.
towerArrangement
Indicates how towers are positioned or organized relative to one another within a given structure or layout.
-
E.
towerDominates
Indicates that one tower stands out over another or its surroundings in a commanding or visually overpowering way.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.