Triple
T13930280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Orme Copper Mines |
E334970
|
entity |
| Predicate | estimatedWorkingsLength |
P112331
|
FINISHED |
| Object | several kilometres of tunnels |
—
|
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: several kilometres of tunnels | Statement: [Great Orme Copper Mines, estimatedWorkingsLength, several kilometres of tunnels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedWorkingsLength Context triple: [Great Orme Copper Mines, estimatedWorkingsLength, several kilometres of tunnels]
-
A.
workLength
Indicates the duration or length of time associated with a particular work or task.
-
B.
workLengthRequirement
Indicates that there is a specified minimum or exact duration of work required for something (e.g., a job, task, or role).
-
C.
materialWorked
Indicates that an agent performs work or processing on a specified material.
-
D.
possibleLengthDays
Indicates that an entity can have a duration, measured in whole or fractional days, equal to the specified value.
-
E.
projectLength
Indicates the duration or total time span over which a project is planned or executed.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa900a0819095eeb1bc46b0336e |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:16 p.m.