Triple
T5919700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Privacy Badger |
E131669
|
entity |
| Predicate | softwareHelpPage |
P67697
|
FINISHED |
| Object | https://privacybadger.org/#faq |
—
|
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: https://privacybadger.org/#faq | Statement: [Privacy Badger, softwareHelpPage, https://privacybadger.org/#faq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareHelpPage Context triple: [Privacy Badger, softwareHelpPage, https://privacybadger.org/#faq]
-
A.
softwareName
Indicates that one entity is the name or title of a software application associated with another entity.
-
B.
softwareLibrary
Indicates that one entity is a software library that provides code, functionality, or services used by another entity.
-
C.
softwareIncluded
Indicates that certain software is bundled with, provided alongside, or contained within another item or offering.
-
D.
softwareMedium
Indicates that something is conveyed, stored, or expressed through a software-based medium or digital environment.
-
E.
usesSoftware
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c048fb02a081908e78629e1e283cd0 |
completed | March 22, 2026, 7:54 p.m. |
Created at: March 22, 2026, 4 p.m.