Triple
T18567516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punycode |
E453792
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | IDNA2008 |
—
|
NE NERFINISHED |
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: IDNA2008 | Statement: [Punycode, relatedTo, IDNA2008]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IDNA2008 Context triple: [Punycode, relatedTo, IDNA2008]
-
A.
Internationalizing Domain Names in Applications (IDNA)
chosen
Internationalizing Domain Names in Applications (IDNA) is a technical standard that enables the use of non-ASCII, internationalized characters in domain names while maintaining compatibility with the existing DNS infrastructure.
-
B.
Unicode Technical Standard #10
Unicode Technical Standard #10 is the specification that defines the Unicode Collation Algorithm, providing a standardized method for comparing and sorting Unicode text across languages and platforms.
-
C.
Lightweight Directory Access Protocol (LDAP): Internationalized String Preparation
"Lightweight Directory Access Protocol (LDAP): Internationalized String Preparation" is an IETF specification (RFC 4518) that defines how to prepare and compare internationalized character strings used in LDAP directories to ensure consistent, interoperable matching.
-
D.
Unicode Technical Standard #35
Unicode Technical Standard #35 is a Unicode Consortium specification that defines the Locale Data Markup Language (LDML) and related mechanisms for internationalization, including formatting of dates, times, numbers, and other locale-sensitive data.
-
E.
Unicode Standard Annex #38
Unicode Standard Annex #38 is a technical report that defines the Unicode Han Database (Unihan), specifying data fields and properties for East Asian ideographs used in the Unicode Standard.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53affc3e08190b4d16b5ccb0bddbc |
completed | April 19, 2026, 8:28 p.m. |
Created at: April 10, 2026, 11:43 a.m.