Triple
T33435150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Linking |
E856222
|
entity |
| Predicate | keyHeaderField |
P3703
|
FINISHED |
| Object | Link |
—
|
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: Link | Statement: [Web Linking, keyHeaderField, Link]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyHeaderField Context triple: [Web Linking, keyHeaderField, Link]
-
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.
keyField
Indicates that the referenced field serves as a primary or unique identifier within a data structure or record.
-
C.
keyFieldPost
Indicates a relationship where a key field is associated with or applied to a specific post, typically identifying or indexing that post.
-
D.
keyParameter
Indicates that one entity functions as a primary or critical parameter that significantly influences or determines the behavior, outcome, or configuration of another entity.
-
E.
keyFieldSource
Indicates that one field serves as the originating or primary source for a key value used to identify or link related data.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4857f3c819086399a37e954c6e9 |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.