Triple
T30350800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .info |
E771982
|
entity |
| Predicate | isInternationalized |
P11998
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [.info, isInternationalized, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInternationalized Context triple: [.info, isInternationalized, yes]
-
A.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
B.
isInternationalStandard
Indicates that something has been formally recognized or adopted as a standard at the international level.
-
C.
supportsInternationalization
chosen
Indicates that an entity provides functionality or features that enable use across multiple languages, locales, or regional formats.
-
D.
hasInternationalName
Indicates that an entity is associated with a name used or recognized in an international or cross-linguistic context.
-
E.
hasInternationalField
Indicates that an entity includes or is associated with a field, attribute, or component that pertains to international or cross-border aspects.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 7:56 p.m.