Triple
T16601722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miners |
E403344
|
entity |
| Predicate | thematicOrigin |
P93696
|
FINISHED |
| Object | mining heritage of El Paso region |
—
|
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: mining heritage of El Paso region | Statement: [Miners, thematicOrigin, mining heritage of El Paso region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thematicOrigin Context triple: [Miners, thematicOrigin, mining heritage of El Paso region]
-
A.
hasThematicOrigin
chosen
Indicates that something originates from, or is thematically derived from, a particular source, subject, or theme.
-
B.
primaryThemeOrigin
Indicates that the primary thematic content of something (e.g., a work or discourse) originates from or is derived from a particular source or context.
-
C.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
D.
themedAs
Indicates that something is characterized, styled, or organized according to a particular theme or motif.
-
E.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d764574819081366374ca0c9bea |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.