Triple
T2656025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .rf |
E54610
|
entity |
| Predicate | supportsSecondLevelRegistrations |
P42018
|
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: [.rf, supportsSecondLevelRegistrations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSecondLevelRegistrations Context triple: [.rf, supportsSecondLevelRegistrations, yes]
-
A.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
B.
supportsUnregisteredUse
Indicates that an entity allows or enables the use of something without requiring prior registration or formal enrollment.
-
C.
secondLevelDomain
Indicates that one entity is the second-level domain associated with, or extracted from, another entity such as a full domain name or URL.
-
D.
supportsMultiuser
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
-
E.
registrationMode
Indicates the method or process by which something is registered or enrolled.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abda0ba2208190ad87763ecbef8c3c |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd815d06481909535c02b0aba8553 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abda0a13308190a986df86270258a7 |
completed | March 7, 2026, 7:55 a.m. |
Created at: March 6, 2026, 9:53 p.m.