Triple
T20395278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norsk Hydro |
E500185
|
entity |
| Predicate | laterCoreBusiness |
P44322
|
FINISHED |
| Object | aluminium production |
—
|
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: aluminium production | Statement: [Norsk Hydro, laterCoreBusiness, aluminium production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCoreBusiness Context triple: [Norsk Hydro, laterCoreBusiness, aluminium production]
-
A.
laterBusinessBase
Indicates that one business entity serves as the subsequent or successor base of operations relative to another business entity.
-
B.
laterMainBusiness
chosen
Indicates that one business activity or enterprise occurs after and succeeds another as the main business.
-
C.
formerCoreBusiness
Indicates that an entity was previously the main or primary line of business for another entity but no longer holds that status.
-
D.
laterBusinessModel
Indicates that one business model occurs or is adopted after another in time, representing a subsequent or successor business model in a sequence.
-
E.
laterCoreDesign
Indicates that one design or version serves as a later or subsequent core design relative to another in a development sequence.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67912d7948190ac2fda8ce95e5c70 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.