Triple
T27663172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAA |
E697169
|
entity |
| Predicate | madeMandatoryForCAsBy |
P23639
|
FINISHED |
| Object | CA/Browser Forum Baseline Requirements |
—
|
NE NERFINISHED |
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: CA/Browser Forum Baseline Requirements | Statement: [CAA, madeMandatoryForCAsBy, CA/Browser Forum Baseline Requirements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeMandatoryForCAsBy Context triple: [CAA, madeMandatoryForCAsBy, CA/Browser Forum Baseline Requirements]
-
A.
isMandatoryFor
chosen
Indicates that something is required or compulsory for another thing to occur, be valid, or be completed.
-
B.
mustEstablish
Indicates that one entity is obligated or required to create, set up, or formally establish another entity, condition, or relationship.
-
C.
isMandatoryInSomeJurisdictions
Indicates that the subject is legally required or compulsory in at least one jurisdiction or legal authority.
-
D.
mandatedAcceptanceOf
Indicates that one entity is required, by rule or authority, to accept or approve something from another entity.
-
E.
mustGrant
Indicates that one party is obligated to give or allow something (such as a right, permission, or resource) to another party.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f634a183bc8190bdb59700f8f0a16e |
completed | May 2, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:37 p.m.