Triple
T36624726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IANA |
E904139
|
entity |
| Predicate | managesRegistryFor |
P18296
|
FINISHED |
| Object | DNS parameters |
—
|
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: DNS parameters | Statement: [IANA, managesRegistryFor, DNS parameters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesRegistryFor Context triple: [IANA, managesRegistryFor, DNS parameters]
-
A.
maintainsRegistryOf
chosen
Indicates that one entity is responsible for keeping and updating an official record or list of another set of entities or items.
-
B.
registryManaged
Indicates that an entity is controlled, maintained, or overseen by a central registry or registration authority.
-
C.
registryFor
Indicates a relationship where one entity serves as an official registry or record-keeping authority for another entity or set of items.
-
D.
relatedRegistry
Indicates that one registry has an association or linkage to another registry.
-
E.
managingFor
Indicates that one entity is responsible for directing, supervising, or overseeing activities, resources, or operations on behalf of another entity.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:11 p.m.