Triple
T18567498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punycode |
E453792
|
entity |
| Predicate | domainApplication |
P127764
|
FINISHED |
| Object | internationalized domain names (IDNs) |
—
|
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: internationalized domain names (IDNs) | Statement: [Punycode, domainApplication, internationalized domain names (IDNs)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainApplication Context triple: [Punycode, domainApplication, internationalized domain names (IDNs)]
-
A.
domainComponent
Indicates that one entity is a constituent or functional part of a larger domain or system represented by another entity.
-
B.
componentApplication
Indicates that one entity is an application or use-case instance that is built from, configured by, or otherwise realized through another entity serving as its component.
-
C.
commonApplication
Indicates that multiple entities share or participate in the same application, process, or usage context.
-
D.
definesApplication
Indicates that one entity specifies or establishes the purpose, scope, or behavior of an application associated with another entity.
-
E.
originalApplicationDomain
chosen
Indicates the domain or field in which something was first designed, intended, or primarily applied.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53affc3e08190b4d16b5ccb0bddbc |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.