Triple
T3498834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham Cathedral |
E73914
|
entity |
| Predicate | hasTowerPosition |
P48512
|
FINISHED |
| Object | west end |
—
|
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: west end | Statement: [Birmingham Cathedral, hasTowerPosition, west end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTowerPosition Context triple: [Birmingham Cathedral, hasTowerPosition, west end]
-
A.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
B.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
C.
positionRelativeToTower
Indicates the spatial relationship or placement of an entity with respect to a specified tower.
-
D.
isObservationTower
Indicates that something functions as an observation tower, serving primarily as a structure for viewing or monitoring an area from an elevated position.
-
E.
hasControlTower
Indicates that one entity possesses, hosts, or is equipped with a control tower that manages or oversees its operations.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbd3ad548190abbfae820bf3b66d |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaef1037c819082c7af949ec85360 |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:18 p.m.