Triple
T23402691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botallack Mine |
E559547
|
entity |
| Predicate | operatedAsMineUntil |
P152124
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Botallack Mine, operatedAsMineUntil, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsMineUntil Context triple: [Botallack Mine, operatedAsMineUntil, late 19th century]
-
A.
operatesMine
Indicates that one entity runs, manages, or controls the functioning of a mine belonging to or associated with another entity.
-
B.
operatedUntil
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
C.
wasExtensivelyMinedIn
Indicates that a location or resource was subject to intensive or large-scale mining activity during a specified time or by a specified agent.
-
D.
operatedAsNameUntil
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
-
E.
initiallyOperated
Indicates that an entity first began functioning, being used, or carrying out its intended operation at a specified initial time or under initial conditions.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4e09ccc81909869d2c5f6d68432 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:37 p.m.