Triple
T30350812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .info |
E771982
|
entity |
| Predicate | transferableBetweenRegistrars |
P195354
|
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, transferableBetweenRegistrars, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferableBetweenRegistrars Context triple: [.info, transferableBetweenRegistrars, yes]
-
A.
supportsInternationalRegistrars
Indicates that an entity is compatible with and provides services for registrars operating in multiple countries or international markets.
-
B.
transferableBetweenServers
Indicates that something can be moved or copied from one server to another while preserving its validity or functionality.
-
C.
transferableBetweenWorlds
Indicates that something can be moved or used across different worlds, realms, or dimensions without losing its essential properties or function.
-
D.
transferable
Indicates that a right, property, or obligation can be legally or practically passed from one entity to another.
-
E.
transferAgreement
Indicates a formal arrangement in which ownership, rights, or responsibilities are transferred from one party to another.
- F. None of above. chosen
Provenance (4 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_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: April 29, 2026, 7:56 p.m.