Triple
T18839990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kongsberg Silver Mines |
E460765
|
entity |
| Predicate | ledToEstablishmentOf |
P986
|
FINISHED |
| Object | town of Kongsberg |
—
|
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: town of Kongsberg | Statement: [Kongsberg Silver Mines, ledToEstablishmentOf, town of Kongsberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledToEstablishmentOf Context triple: [Kongsberg Silver Mines, ledToEstablishmentOf, town of Kongsberg]
-
A.
establishes
chosen
Indicates that one entity initiates, creates, or formally sets up another entity, relationship, or state, often giving it official or recognized status.
-
B.
aimedToEstablish
Indicates an intention or effort directed toward creating, founding, or setting up something.
-
C.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
D.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
-
E.
establishedInResponseTo
Indicates that something was created, initiated, or set up as a direct reaction to a specific event, condition, or stimulus.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8e8f57081909edbbcaf56189816 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.