Triple
T32760604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argo Gold Mill and Tunnel |
E837742
|
entity |
| Predicate | tunnelCompletionDate |
P175088
|
FINISHED |
| Object | 1910 |
—
|
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: 1910 | Statement: [Argo Gold Mill and Tunnel, tunnelCompletionDate, 1910]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunnelCompletionDate Context triple: [Argo Gold Mill and Tunnel, tunnelCompletionDate, 1910]
-
A.
substantialCompletionDate
Indicates the date on which a project, work, or obligation is considered substantially complete, meaning the main required work has been finished to the point it can be used for its intended purpose.
-
B.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
C.
cuttingCompletionDate
Indicates the date on which a cutting process or operation is completed.
-
D.
archCompletionDate
Indicates the date on which an architectural element, project, or structure was completed.
-
E.
reliefWellCompletionDate
Indicates the date on which a relief well is fully completed and ready for operation.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:13 a.m.