Triple
T30350789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .info |
E771982
|
entity |
| Predicate | originalRegistryOperator |
P82710
|
FINISHED |
| Object | Afilias |
—
|
NE NERFINISHED |
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: Afilias | Statement: [.info, originalRegistryOperator, Afilias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRegistryOperator Context triple: [.info, originalRegistryOperator, Afilias]
-
A.
initialOperator
Indicates that an entity serves as the first or primary operator initiating a process, action, or operation involving another entity.
-
B.
DNSRegistryOperator
chosen
Indicates that an entity operates or manages a DNS registry service for domain names.
-
C.
maintainsRegistryOf
Indicates that one entity is responsible for keeping and updating an official record or list of another set of entities or items.
-
D.
coreOperator
Indicates that an entity functions as a primary or central operator responsible for executing or managing a core operation within a system or process.
-
E.
defaultRegistry
Indicates that one entity serves as the primary or standard registry used by another entity in the absence of a specifically chosen alternative.
- 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_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
Created at: April 29, 2026, 7:56 p.m.