Triple
T8445975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinto River |
E199676
|
entity |
| Predicate | miningSince |
P18135
|
FINISHED |
| Object | at least Bronze Age |
—
|
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: at least Bronze Age | Statement: [Tinto River, miningSince, at least Bronze Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miningSince Context triple: [Tinto River, miningSince, at least Bronze Age]
-
A.
minedSince
chosen
Indicates that a resource or material has been extracted from a location continuously starting from a specified point in time.
-
B.
miningStarted
Indicates that the process of extracting resources from a source or site has begun.
-
C.
miningHistory
Indicates a historical record or past occurrence of mining-related activities or operations associated with an entity.
-
D.
firstBlockMinedDate
Indicates the date on which the first block associated with the entity was mined.
-
E.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe3152a3c819092efdeab718def7a |
completed | March 31, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.