Triple
T25535327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silk Browser |
E640024
|
entity |
| Predicate | softwareEngine |
P158634
|
FINISHED |
| Object | Blink |
—
|
NE NERFINISHED |
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 | Statement: [Silk Browser, softwareEngine, Blink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareEngine Context triple: [Silk Browser, softwareEngine, Blink]
-
A.
softwareSystem
Indicates a relationship where an entity functions as, or is classified as, a software system.
-
B.
softwareDomain
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
-
C.
developedSoftware
Indicates that one entity created, programmed, or significantly contributed to the creation of a particular software system or application for another entity or purpose.
-
D.
developsSoftwareIn
Indicates that one entity creates or engineers software within, or for use in, a particular organization, project, or environment.
-
E.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f866376081909ab76a8aa5c3fea7 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 3:22 p.m.