Triple
T32542418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | locally decodable codes |
E831746
|
entity |
| Predicate | decoderAccessPattern |
P79849
|
FINISHED |
| Object | non-adaptive queries |
—
|
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: non-adaptive queries | Statement: [locally decodable codes, decoderAccessPattern, non-adaptive queries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decoderAccessPattern Context triple: [locally decodable codes, decoderAccessPattern, non-adaptive queries]
-
A.
accessPattern
chosen
Indicates how an entity interacts with or retrieves data or resources, such as the manner, frequency, or sequence of access.
-
B.
acquisitionPattern
Indicates the characteristic way in which one entity acquires or obtains another entity or resource, such as the method, frequency, or structure of the acquisition.
-
C.
distributionPattern
Indicates the characteristic way in which something is spread, arranged, or allocated across a space, group, or set.
-
D.
decoderType
Indicates the specific kind or category of decoder associated with or used by an entity.
-
E.
transmissionPattern
Indicates how something is passed or spread from one entity to another, such as the mode or route of transmission.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57fc940819086d7ab256f2cad71 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.