Triple
T30074231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Jakobus Church |
E764272
|
entity |
| Predicate | hasBellTowerCount |
P180152
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [St. Jakobus Church, hasBellTowerCount, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBellTowerCount Context triple: [St. Jakobus Church, hasBellTowerCount, 2]
-
A.
hasBellTower
Indicates that one entity (typically a building or structure) possesses or includes a bell tower as part of it.
-
B.
hasBellTowerLocation
Indicates the specific location where a bell tower is situated or attached relative to another structure or place.
-
C.
hasBellTowerUse
Indicates that an entity is used as, or functions in the capacity of, a bell tower.
-
D.
hasBellTowerHeightSignificance
Indicates that the height of a bell tower holds particular importance or relevance in a given context or relationship.
-
E.
hasBellChamber
Indicates that an entity possesses or includes a bell chamber as one of its structural or functional components.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 29, 2026, 7:01 p.m.