Triple
T32751406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Victoria Colliery |
E837508
|
entity |
| Predicate | operatorAfterClosure |
P201860
|
FINISHED |
| Object | National Mining Museum Scotland |
—
|
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: National Mining Museum Scotland | Statement: [Lady Victoria Colliery, operatorAfterClosure, National Mining Museum Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAfterClosure Context triple: [Lady Victoria Colliery, operatorAfterClosure, National Mining Museum Scotland]
-
A.
operatorBeforeClosure
Indicates that an operator entity occurs or is applied before a closure event or state in a process or sequence.
-
B.
conditionAfterClosure
Indicates the state or circumstances that exist after a process, event, or entity has been formally closed or concluded.
-
C.
postClosureOperator
Indicates that one entity functions as a closure-like operator applied after another operation or process, producing a resulting state or outcome.
-
D.
operatorAfterCapture
Indicates that one operator or action is applied immediately after a capture event has occurred.
-
E.
operatorLater
Indicates that one operator or operation occurs at a later time than another in a temporal ordering.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
| PDg | Predicate description generation | batch_6a002ae65e0c81909a5989dd73f027f5 |
completed | May 10, 2026, 6:51 a.m. |
Created at: May 1, 2026, 1:12 a.m.