Triple
T14040445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Batten |
E337830
|
entity |
| Predicate | MountBattenTowerInstanceOf |
P112596
|
FINISHED |
| Object | artillery tower |
—
|
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: artillery tower | Statement: [Mount Batten, MountBattenTowerInstanceOf, artillery tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MountBattenTowerInstanceOf Context triple: [Mount Batten, MountBattenTowerInstanceOf, artillery tower]
-
A.
BigBenContains
Indicates that Big Ben spatially encloses or holds the referenced entity within its structure.
-
B.
towerLocation
Indicates that a tower is located at, or associated with, a specific place or geographic location.
-
C.
timeballTowerBuilt
Indicates that a time ball tower was constructed or built at a certain time or by a certain agent.
-
D.
towerAttachment
Indicates that one entity is physically attached to or structurally connected with a tower.
-
E.
towerName
Indicates the specific name assigned to a tower in the relationship.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de311814e48190adb637e1c97c0658 |
completed | April 14, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:20 p.m.