Triple
T5688681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Content Security Policy |
E125374
|
entity |
| Predicate | headerName |
P3703
|
FINISHED |
| Object | Content-Security-Policy |
—
|
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: Content-Security-Policy | Statement: [Content Security Policy, headerName, Content-Security-Policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headerName Context triple: [Content Security Policy, headerName, Content-Security-Policy]
-
A.
headerField
chosen
Indicates that one entity is a specific header field (such as a name–value pair) belonging to or defined within another entity, typically a message, request, or document header.
-
B.
headDisplayedBy
Indicates that a particular head (e.g., of a character, avatar, or object) is being visually shown or rendered by a specific display context or system.
-
C.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
-
D.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
E.
hasHeading
Indicates that one entity serves as a heading or title for another entity.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.