Triple
T37339059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cliff Mine |
E926979
|
entity |
| Predicate | endOfMajorOperations |
P184901
|
FINISHED |
| Object | 1870s |
—
|
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: 1870s | Statement: [Cliff Mine, endOfMajorOperations, 1870s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfMajorOperations Context triple: [Cliff Mine, endOfMajorOperations, 1870s]
-
A.
endOfUsefulOperations
chosen
Indicates that the useful or intended operations of an entity, process, or system have been completed or can no longer be effectively performed.
-
B.
finalOperations
Indicates that an entity is involved in the last or concluding set of actions or processes within a sequence or workflow.
-
C.
eraOfMajorOperation
Indicates the historical period during which a major operation primarily took place or was most active.
-
D.
majorOperation
Indicates that one entity performs or undergoes a significant, large-scale, or primary operation or procedure involving another entity or context.
-
E.
endOfUndergroundOperation
Indicates the point in time or event at which an underground operation or activity is concluded or terminated.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.