Triple
T14318956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IDN ccTLD Fast Track |
E355029
|
entity |
| Predicate | technicalBasis |
P38305
|
FINISHED |
| Object | IDNA standards |
—
|
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: IDNA standards | Statement: [IDN ccTLD Fast Track, technicalBasis, IDNA standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technicalBasis Context triple: [IDN ccTLD Fast Track, technicalBasis, IDNA standards]
-
A.
technicalCrux
Indicates a key technical challenge or bottleneck that critically determines the feasibility or success of a solution or system.
-
B.
technologyBasis
chosen
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
-
C.
isTechnical
Indicates that an entity possesses specialized technical knowledge, skills, or characteristics related to technology, engineering, or applied sciences.
-
D.
technicalType
Indicates the specific technical category or classification that characterizes how something is implemented, structured, or functions.
-
E.
technicalGrade
Indicates the level or classification of technical quality, complexity, or proficiency assigned to something.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883a93548190ac671b001d15d0bd |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.