Triple
T26399244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3164 |
E663653
|
entity |
| Predicate | specifiesEncoding |
P7661
|
FINISHED |
| Object | US-ASCII |
—
|
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: US-ASCII | Statement: [RFC 3164, specifiesEncoding, US-ASCII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesEncoding Context triple: [RFC 3164, specifiesEncoding, US-ASCII]
-
A.
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.
-
B.
requestEncoding
Indicates that one entity asks another to use or provide a specific encoding format for data or communication.
-
C.
UTF16Encoding
Indicates that a text value is encoded using the UTF-16 character encoding scheme, defining how its characters are represented as 16-bit code units.
-
D.
encodedInUnicodeSince
Indicates that a given character or symbol has been included and assigned a code point in the Unicode standard starting from a specific version or time.
-
E.
usesCharacterSet
chosen
Indicates that one entity employs or relies on a specific character set defined by another entity for encoding or representing text.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 26, 2026, 11:30 p.m.