Triple
T8486702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Content-Language |
E200848
|
entity |
| Predicate | languageTagStandard |
P6195
|
FINISHED |
| Object | RFC 5646 |
E682197
|
NE 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: RFC 5646 | Statement: [Content-Language, languageTagStandard, RFC 5646]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5646 Context triple: [Content-Language, languageTagStandard, RFC 5646]
-
A.
IETF BCP 47
chosen
IETF BCP 47 is the Internet standard that defines the structure and use of language tags for identifying human languages and related variants in digital systems.
-
B.
ISO 15924
ISO 15924 is an international standard that assigns four-letter codes to the world’s writing systems and scripts for use in information processing and interchange.
-
C.
SSH Language Tags
SSH Language Tags are standardized identifiers used within the SSH protocol to specify human languages for messages and data, enabling proper localization and internationalization.
-
D.
ISO 639
ISO 639 is an international standard that defines codes for the representation of names of languages.
-
E.
RFC 2579
RFC 2579 is an Internet standards document that defines textual conventions for use with the Structure of Management Information Version 2 (SMIv2) in network management protocols like SNMP.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4576d48c8190a3e94d8ab3001b65 |
completed | March 31, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4df197c48190812c5287119e5528 |
completed | April 2, 2026, 11:07 a.m. |
Created at: March 30, 2026, 6:13 p.m.