Triple
T8486606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accept-Language |
E200846
|
entity |
| Predicate | defaultQValue |
P83550
|
FINISHED |
| Object | 1.0 |
—
|
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: 1.0 | Statement: [Accept-Language, defaultQValue, 1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultQValue Context triple: [Accept-Language, defaultQValue, 1.0]
-
A.
defaultPosition
Indicates the standard or initial spatial arrangement or pose that an entity assumes in the absence of other specified positions.
-
B.
defaultNameValue
Indicates that an entity is assigned a standard or fallback name value used when no specific name has been provided.
-
C.
defaultOn
Indicates that something is in an enabled or active state by default, without requiring explicit activation.
-
D.
defaultBehavior
Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
-
E.
defaultParameterSet
Indicates that a particular set of parameters is designated as the standard or fallback configuration to be used when no other specific parameter set is provided.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53c4d608190a766c0e919a4b96f |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.