Triple
T33433307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Referer HTTP header |
E856186
|
entity |
| Predicate | hasMisspellingOrigin |
P190077
|
FINISHED |
| Object | Referrer |
—
|
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: Referrer | Statement: [Referer HTTP header, hasMisspellingOrigin, Referrer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMisspellingOrigin Context triple: [Referer HTTP header, hasMisspellingOrigin, Referrer]
-
A.
hasVariantSpelling
Indicates that one term is an alternative spelling form of another term.
-
B.
spellingStatus
Indicates the correctness or condition of the spelling of a given text or term.
-
C.
originalSpelling
Indicates that one entity provides the initial or historically first-used spelling form of another entity’s name or term.
-
D.
hasTypicalSpelling
Indicates that one form is the standard or commonly accepted spelling of another form.
-
E.
hasSpellingWithAccent
Indicates that one form of a word or name is spelled using accented characters compared to another form.
- F. None of above. chosen
Provenance (4 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_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: May 1, 2026, 1:36 a.m.