Triple
T8486585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accept-Encoding |
E200845
|
entity |
| Predicate | fieldValueType |
P4541
|
FINISHED |
| Object | list of codings with optional quality values |
—
|
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: list of codings with optional quality values | Statement: [Accept-Encoding, fieldValueType, list of codings with optional quality values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldValueType Context triple: [Accept-Encoding, fieldValueType, list of codings with optional quality values]
-
A.
fieldType
chosen
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
-
B.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
-
C.
logicalType
Indicates that one entity is classified as a logical type or category used to define or constrain the logical behavior or interpretation of another entity.
-
D.
columnType
Indicates the specific data type assigned to a column within a table or dataset.
-
E.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
- 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_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. |
Created at: March 30, 2026, 6:13 p.m.