Triple
T33697351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presto layout engine |
E863349
|
entity |
| Predicate | replacedByInOpera |
P143023
|
FINISHED |
| Object | Blink-based engine |
—
|
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: Blink-based engine | Statement: [Presto layout engine, replacedByInOpera, Blink-based engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByInOpera Context triple: [Presto layout engine, replacedByInOpera, Blink-based engine]
-
A.
replacedOnPlatformBy
chosen
Indicates that one entity has been superseded or taken over by another entity on a particular platform.
-
B.
replacedByInProduction
Indicates that one entity has been superseded and is no longer used in production because another specified entity has taken its place.
-
C.
oftenReplacedBy
Indicates that one entity is frequently substituted or superseded by another in similar contexts or uses.
-
D.
replacedByInUnity
Indicates that one entity has been superseded or substituted by another entity within the context of Unity.
-
E.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:43 a.m.