Triple
T110413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | open-hearth process |
E2235
|
entity |
| Predicate | supplantedBy |
P101
|
FINISHED |
| Object | basic oxygen process |
—
|
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: basic oxygen process | Statement: [open-hearth process, supplantedBy, basic oxygen process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supplantedBy Context triple: [open-hearth process, supplantedBy, basic oxygen process]
-
A.
wasSupersededBy
chosen
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
-
C.
subordinateTo
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
-
D.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
E.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with another entity.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258b58efc8190959c86f73d67b744 |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25641058c8190b5b64509b35d8176 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.