Triple
T35077948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPAPI |
E1012354
|
entity |
| Predicate | relationToNPAPI |
P107867
|
FINISHED |
| Object | more secure than NPAPI |
—
|
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: more secure than NPAPI | Statement: [PPAPI, relationToNPAPI, more secure than NPAPI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToNPAPI Context triple: [PPAPI, relationToNPAPI, more secure than NPAPI]
-
A.
advantageOverNPAPI
chosen
Indicates that one entity has a benefit or superiority compared to the NPAPI technology or approach.
-
B.
relatedInterface
Indicates that one interface is associated or connected to another interface in a relevant or dependent way.
-
C.
relationToAppleTalk
Indicates a relationship or association between an entity and AppleTalk, such as compatibility, usage, support, or interaction with the AppleTalk networking protocol.
-
D.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
E.
relatedToInterface
Indicates a relationship where one entity is associated with, concerns, or is relevant to a particular interface.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.