Triple
T38029824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sambian Peninsula |
E948876
|
entity |
| Predicate | amberMining |
P105168
|
FINISHED |
| Object | hasLongHistory |
—
|
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: hasLongHistory | Statement: [Sambian Peninsula, amberMining, hasLongHistory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amberMining Context triple: [Sambian Peninsula, amberMining, hasLongHistory]
-
A.
miningSite
chosen
Indicates a location where mining activities or mineral extraction operations take place.
-
B.
mineName
Indicates that an entity has or is associated with a specific mine identified by a given name.
-
C.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
-
D.
miningCompany
Indicates a relationship where an entity operates as a company engaged in the extraction of natural resources from the earth.
-
E.
discoveryOfOre
Indicates the event or relationship in which a particular ore deposit is found, identified, or recognized, typically linking the discoverer, the ore, and the location or time of discovery.
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc999ba0081908ec76b8a771bf071 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.