Triple
T6034428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EdgeHTML |
E134381
|
entity |
| Predicate | replacedByInProduct |
P49726
|
FINISHED |
| Object | Chromium engine in Microsoft Edge |
—
|
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: Chromium engine in Microsoft Edge | Statement: [EdgeHTML, replacedByInProduct, Chromium engine in Microsoft Edge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByInProduct Context triple: [EdgeHTML, replacedByInProduct, Chromium engine in Microsoft Edge]
-
A.
replacedInProduct
chosen
Indicates that one component or element in a product has been substituted or superseded by another component or element within that product.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
D.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
E.
replacedInSomeWorkflowsBy
Indicates that in certain workflows or processes, one entity is substituted or superseded by another.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b33a7c8190ad6282286199b192 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.