Triple
T7696949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcoa |
E174392
|
entity |
| Predicate | keyMaterial |
P78339
|
FINISHED |
| Object | bauxite ore |
—
|
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: bauxite ore | Statement: [Alcoa, keyMaterial, bauxite ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyMaterial Context triple: [Alcoa, keyMaterial, bauxite ore]
-
A.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
B.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
C.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
-
D.
keyExport
Indicates that a cryptographic key is transferred or made available from one system, location, or format to another.
-
E.
keyOperation
Indicates an operation that is central, primary, or essential to the functioning or outcome of another process, system, or relationship.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:03 p.m.