Triple
T19624671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nantwich salt field |
E471103
|
entity |
| Predicate | exploitedSince |
P111259
|
FINISHED |
| Object | Roman times |
—
|
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: Roman times | Statement: [Nantwich salt field, exploitedSince, Roman times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploitedSince Context triple: [Nantwich salt field, exploitedSince, Roman times]
-
A.
exploitedFor
Indicates that one entity is unfairly or abusively used by another entity as a resource, means, or advantage for the latter’s benefit.
-
B.
exploitationBegan
chosen
Indicates the point in time when the exploitation or use of a resource, person, or system was initiated.
-
C.
эксплуатируется
Indicates that one entity is being used or operated by another, often in a way that takes advantage of its resources, capabilities, or labor.
-
D.
exploits
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
-
E.
coveredSince
Indicates that one entity has been under the protection, applicability, or effect of another entity continuously starting from a specified point in time.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e92ff48190ae6e6ba2c603d5e7 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.