Triple
T35201787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilmanstone Colliery |
E1016425
|
entity |
| Predicate | hasShaft |
P155012
|
FINISHED |
| Object | Tilmanstone Colliery No. 1 shaft |
—
|
NE NERFINISHED |
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: Tilmanstone Colliery No. 1 shaft | Statement: [Tilmanstone Colliery, hasShaft, Tilmanstone Colliery No. 1 shaft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShaft Context triple: [Tilmanstone Colliery, hasShaft, Tilmanstone Colliery No. 1 shaft]
-
A.
hasShafts
chosen
Indicates that one entity possesses or is equipped with one or more shafts as components or structural elements.
-
B.
hasPubliclyAccessibleShaft
Indicates that an entity possesses a shaft (such as a tunnel, elevator, or similar vertical/horizontal passage) that is accessible for use or entry by the general public.
-
C.
shaftFeature
Indicates a relationship where one object possesses or is characterized by a shaft-like structural feature.
-
D.
typicalShaftType
Indicates the usual or characteristic type of shaft associated with an entity or configuration.
-
E.
axeShaftColor
Indicates the color attribute associated with the shaft (handle) of an axe.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:02 p.m.