Triple
T17234443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrome security policies |
E418321
|
entity |
| Predicate | enforcedAt |
P31667
|
FINISHED |
| Object | browser runtime |
—
|
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: browser runtime | Statement: [Chrome security policies, enforcedAt, browser runtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcedAt Context triple: [Chrome security policies, enforcedAt, browser runtime]
-
A.
enforcedOn
chosen
Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
-
B.
enactedAfter
Indicates that one enactment event occurred later in time than another enactment event.
-
C.
enforcedProvision
Indicates that an authority or agent compelled compliance with a specific rule, term, or provision.
-
D.
inForceSince
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
-
E.
endorsedAt
Indicates the specific time or date at which an endorsement or approval of something was made.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dfa0a408190880804d463305867 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.