Triple
T32062143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADIF |
E818772
|
entity |
| Predicate | encodingMode |
P33682
|
FINISHED |
| Object | supports constant bit rate AAC |
—
|
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: supports constant bit rate AAC | Statement: [ADIF, encodingMode, supports constant bit rate AAC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodingMode Context triple: [ADIF, encodingMode, supports constant bit rate AAC]
-
A.
encodingSelection
Indicates that an entity chooses or specifies a particular encoding method or format to be used in a given context.
-
B.
dataEncodingMethod
chosen
Indicates the specific technique or format used to encode data for storage, transmission, or processing.
-
C.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
D.
compressionMode
Indicates the specific method or setting used to compress data or content in a given context.
-
E.
encodes
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f638908190957f64096c07535f |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:22 a.m.