Triple
T28694106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katanga |
E729364
|
entity |
| Predicate | importantResource |
P152223
|
FINISHED |
| Object | copper |
—
|
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: copper | Statement: [Katanga, importantResource, copper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantResource Context triple: [Katanga, importantResource, copper]
-
A.
importantObject
Indicates that one entity is considered especially significant, central, or of high priority in relation to another entity or context.
-
B.
significantResource
chosen
Indicates that one entity serves as an important or substantial resource (e.g., material, financial, informational, or human) for another entity.
-
C.
importantSaint
Indicates that the subject is recognized as a particularly significant or highly revered saint within a religious or spiritual tradition.
-
D.
importantNote
Indicates that one entity is marked as an important or noteworthy note in relation to another entity.
-
E.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 5:38 a.m.