Triple
T26092719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6890 |
E658168
|
entity |
| Predicate | registryMaintainer |
P18296
|
FINISHED |
| Object | Internet Assigned Numbers Authority |
—
|
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: Internet Assigned Numbers Authority | Statement: [RFC 6890, registryMaintainer, Internet Assigned Numbers Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registryMaintainer Context triple: [RFC 6890, registryMaintainer, Internet Assigned Numbers Authority]
-
A.
registryManaged
Indicates that an entity is controlled, maintained, or overseen by a central registry or registration authority.
-
B.
maintainsRegistryOf
chosen
Indicates that one entity is responsible for keeping and updating an official record or list of another set of entities or items.
-
C.
registryType
Indicates the specific category or classification of a registry that an entity is associated with or recorded in.
-
D.
registryFunction
Indicates a function that is responsible for registering or recording entities, configurations, or events within a registry or central management system.
-
E.
registryName
Indicates that an entity is identified or labeled by a specific name within a registry or registration system.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f607335d60819081808e1a52941262 |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:48 p.m.