Triple
T2050927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 783 |
E45563
|
entity |
| Predicate | definesFileNameEncoding |
P20982
|
FINISHED |
| Object | netascii for text files |
—
|
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: netascii for text files | Statement: [RFC 783, definesFileNameEncoding, netascii for text files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesFileNameEncoding Context triple: [RFC 783, definesFileNameEncoding, netascii for text files]
-
A.
fileName
Indicates the name assigned to a file, typically used to identify or reference that file within a system or context.
-
B.
codingSystemType
chosen
Indicates the classification or category of coding system used to encode or represent information in a given context.
-
C.
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.
-
D.
maximumFileNameLength
Indicates the maximum number of characters allowed in a file name within a given system or context.
-
E.
hasUnicodeName
Indicates that an entity is associated with a specific official Unicode name assigned to a character or symbol.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb98f5f4881908d9aa0f10be44041 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.