Triple
T12515231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | a.out |
E299176
|
entity |
| Predicate | hasHeaderField |
P3703
|
FINISHED |
| Object | magic number |
—
|
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: magic number | Statement: [a.out, hasHeaderField, magic number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeaderField Context triple: [a.out, hasHeaderField, magic number]
-
A.
hasHeaderName
Indicates that an entity (such as a header or column) bears or is identified by a specific name.
-
B.
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.
-
C.
hasFieldName
Indicates that one entity is associated with, or identified by, a specific field name in a data structure or schema.
-
D.
isRequestHeader
Indicates that something functions as an HTTP request header, i.e., a name–value pair sent by a client to provide metadata or control information for an HTTP request.
-
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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.