Triple
T18531815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slim CSRF |
E452847
|
entity |
| Predicate | tokenTransport |
P105413
|
FINISHED |
| Object | hidden form fields |
—
|
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: hidden form fields | Statement: [Slim CSRF, tokenTransport, hidden form fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tokenTransport Context triple: [Slim CSRF, tokenTransport, hidden form fields]
-
A.
bearerType
Indicates the type or category of entity that serves as the bearer or holder in a given relationship or context.
-
B.
sessionTransport
chosen
Indicates a relationship where a session is carried or conveyed using a particular transport mechanism or protocol.
-
C.
tokenType
Indicates the classification or category assigned to a token within a sequence, such as its syntactic, semantic, or functional role.
-
D.
nativeToken
Indicates that the referenced token is the primary, built-in cryptocurrency or asset of a given blockchain or platform, as opposed to a secondary or issued token.
-
E.
bearerField
Indicates that one entity serves as the bearer or holder of a specific field, attribute, or property associated with 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533fe35288190977c85ee0bb96264 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.