Triple
T29440469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8011 |
E746696
|
entity |
| Predicate | definesEncoding |
P177025
|
FINISHED |
| Object | IPP binary encoding |
—
|
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: IPP binary encoding | Statement: [RFC 8011, definesEncoding, IPP binary encoding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesEncoding Context triple: [RFC 8011, definesEncoding, IPP binary encoding]
-
A.
encodingIs
chosen
Indicates that one entity serves as the specific encoding or coded representation of another entity.
-
B.
usesEncodingRules
Indicates that one entity applies or conforms to a specified set of encoding rules when representing or transforming information.
-
C.
dataEncodingMethod
Indicates the specific technique or format used to encode data for storage, transmission, or processing.
-
D.
localEncoding
Indicates that an entity is represented or stored using a specific encoding scheme that is defined or applied locally within a particular context or system.
-
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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 28, 2026, 3:21 p.m.