Triple
T29577418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiatura |
E753479
|
entity |
| Predicate | usedToSupply |
P17063
|
FINISHED |
| Object | manganese for Soviet industry |
—
|
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: manganese for Soviet industry | Statement: [Chiatura, usedToSupply, manganese for Soviet industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToSupply Context triple: [Chiatura, usedToSupply, manganese for Soviet industry]
-
A.
suppliesTo
chosen
Indicates that one entity provides or delivers goods, services, or resources to another entity.
-
B.
usedSupplyMethod
Indicates that an entity employed a particular method or process to supply or deliver something.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
supplyBy
Indicates that one entity is provided, furnished, or made available by another entity as its source or supplier.
-
E.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 6:04 p.m.