Triple
T18724915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WARC |
E457874
|
entity |
| Predicate | headerFormat |
P3703
|
FINISHED |
| Object | text-based key-value headers |
—
|
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: text-based key-value headers | Statement: [WARC, headerFormat, text-based key-value headers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headerFormat Context triple: [WARC, headerFormat, text-based key-value headers]
-
A.
header
Indicates that one entity serves as a heading or title section that precedes and organizes the content of another entity.
-
B.
headerCategory
Indicates that one entity serves as a categorical grouping or classification for the header or heading represented by the other entity.
-
C.
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.
-
D.
headWriter
Indicates that one entity serves as the principal or lead writer responsible for the creative or written content associated with another entity.
-
E.
headerFile
Indicates that one file serves as a header file for another file, typically declaring interfaces, types, or constants used by that other file.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d72d2c4819080b0d31860976b5e |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:50 a.m.