Triple
T25312316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .pl country-code top-level domain |
E634638
|
entity |
| Predicate | IDNScript |
P150428
|
FINISHED |
| Object | Polish |
—
|
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: Polish | Statement: [.pl country-code top-level domain, IDNScript, Polish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IDNScript Context triple: [.pl country-code top-level domain, IDNScript, Polish]
-
A.
IDNSupport
Indicates that an entity provides or enables support for Internationalized Domain Names (IDNs), such as registering, resolving, or handling domain names with non-ASCII characters.
-
B.
scriptInventor
Indicates that one entity is the creator or originator of a particular writing system or script used by another entity.
-
C.
scriptName
Indicates the name or title of a script associated with an entity, typically identifying which script is used, referenced, or executed in a given context.
-
D.
scriptNameLanguage
Indicates that a script’s name is expressed or written in a particular language.
-
E.
usesScriptFor
chosen
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4939f4e58819095eba5792f55f07c |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:27 p.m.