Triple
T15142778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DatPiff |
E361727
|
entity |
| Predicate | supportsAccessVia |
P93561
|
FINISHED |
| Object | web browser |
—
|
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: web browser | Statement: [DatPiff, supportsAccessVia, web browser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAccessVia Context triple: [DatPiff, supportsAccessVia, web browser]
-
A.
supportsAccessModel
chosen
Indicates that one entity enables, permits, or is compatible with a particular access model used by another entity.
-
B.
supportsCLIAccess
Indicates that one entity enables or allows another entity to access a Command Line Interface (CLI).
-
C.
supportsACLs
Indicates that one entity provides or is compatible with access control lists (ACLs) for managing permissions on another entity.
-
D.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
E.
assumesAccessTo
Indicates that one entity presupposes or takes for granted that it has access to another entity, resource, or piece of information.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c5c4248190b57234e3ccf2831b |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.