Triple
T16702627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firefox Monitor |
E405888
|
entity |
| Predicate | doesNotRequireRegistrationFor |
P64000
|
FINISHED |
| Object | single email breach lookup |
—
|
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: single email breach lookup | Statement: [Firefox Monitor, doesNotRequireRegistrationFor, single email breach lookup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotRequireRegistrationFor Context triple: [Firefox Monitor, doesNotRequireRegistrationFor, single email breach lookup]
-
A.
isNotRequiredFor
Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
-
B.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
C.
canBeUsedWithout
chosen
Indicates that one entity is capable of functioning or being utilized independently of another specified entity.
-
D.
doesNotAutomaticallyProvide
Indicates that something is not supplied or made available by default and requires an explicit action or request to be provided.
-
E.
registrationFor
Indicates a relationship where one entity is enrolled, signed up, or formally recorded to participate in, use, or be associated with another entity (such as an event, service, or program).
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38333a6908190a17d2dee2ca622d6 |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.