Triple
T31080765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCSP |
E792087
|
entity |
| Predicate | mayLeak |
P165909
|
FINISHED |
| Object | client browsing behavior if queried directly |
—
|
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: client browsing behavior if queried directly | Statement: [OCSP, mayLeak, client browsing behavior if queried directly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayLeak Context triple: [OCSP, mayLeak, client browsing behavior if queried directly]
-
A.
stillLeaks
Indicates that an entity continues to leak despite prior attempts or the passage of time.
-
B.
leaks
chosen
Indicates that a substance, information, or resource escapes or is released unintentionally from its intended container, system, or source.
-
C.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
D.
leakedFrom
Indicates that information, material, or content has been disclosed or escaped from a particular source, typically without authorization.
-
E.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.