Triple
T33161622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William T. Coleman |
E848756
|
entity |
| Predicate | roleInMining |
P162289
|
FINISHED |
| Object | development of borax mining operations |
—
|
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: development of borax mining operations | Statement: [William T. Coleman, roleInMining, development of borax mining operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMining Context triple: [William T. Coleman, roleInMining, development of borax mining operations]
-
A.
miningRole
chosen
Indicates a role or function specifically associated with performing or supporting mining activities.
-
B.
roleInDUNE
Indicates that an entity has a specific acting role or participation in the production of the film "Dune."
-
C.
isMinedIn
Indicates that a resource or material is extracted or obtained from a particular location or site.
-
D.
minerRepresents
Indicates that a miner acts on behalf of, or serves as a representative or proxy for, another entity in a given context.
-
E.
roleInGoldRush
Indicates that an entity played a specific role or had a particular involvement in the historical event known as the Gold Rush.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: May 1, 2026, 1:28 a.m.