Triple
T20545421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thio |
E504456
|
entity |
| Predicate | hasMiningActivitySince |
P18135
|
FINISHED |
| Object | 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: 19th century | Statement: [Thio, hasMiningActivitySince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningActivitySince Context triple: [Thio, hasMiningActivitySince, 19th century]
-
A.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
B.
minedSince
chosen
Indicates that a resource or material has been extracted from a location continuously starting from a specified point in time.
-
C.
hasEvidenceOfActivitySince
Indicates that there is evidence showing an entity has been active or engaged in some activity from a specified point in time onward.
-
D.
hasRecentActivity
Indicates that the subject has performed an action or been involved in an event within a defined recent time period.
-
E.
hasNotableMine
Indicates that an entity possesses or is associated with a mine considered significant or noteworthy in some context.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a29684648190969d8fc23743e288 |
completed | April 20, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.