Triple
T19768932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susuman |
E474829
|
entity |
| Predicate | foundedAsSettlementFor |
P137261
|
FINISHED |
| Object | gold 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: gold mining operations | Statement: [Susuman, foundedAsSettlementFor, gold mining operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsSettlementFor Context triple: [Susuman, foundedAsSettlementFor, gold mining operations]
-
A.
foundedAsResidenceOf
Indicates that something was originally established or created to serve as the residence of a particular person or group.
-
B.
foundedAsModernSettlement
Indicates that one entity was established or created as a modern-era settlement, rather than originating as an ancient or historical habitation.
-
C.
originOfSettlement
Indicates the place, source, or starting point from which a settlement was established or originated.
-
D.
foundedAsCityBy
Indicates that a city was originally established or created by a specific person, group, or authority.
-
E.
placeFounded
Indicates the location where an entity (such as an organization or institution) was originally established or founded.
- F. None of above. chosen
Provenance (4 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65359bb9881908f48282b63a83f2f |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:48 p.m.