Triple
T16308491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BV |
E395982
|
entity |
| Predicate | tldStatus |
P82713
|
FINISHED |
| Object | not in use |
—
|
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: not in use | Statement: [BV, tldStatus, not in use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tldStatus Context triple: [BV, tldStatus, not in use]
-
A.
TLDType
Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
-
B.
legalStatusOfName
Indicates the legal status or validity of a given name within a formal or regulatory context.
-
C.
ICANNDelegationStatus
chosen
Indicates the current status or outcome of ICANN’s delegation or redelegation decision for a particular top-level domain within the DNS.
-
D.
ICANNApproved
Indicates that an entity (such as a domain, registrar, or policy) has been formally reviewed and granted approval by ICANN, the Internet Corporation for Assigned Names and Numbers.
-
E.
managesTopLevelDomain
Indicates that one entity has administrative authority over and is responsible for operating and maintaining a specific top-level domain on the internet.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288d776808190a7c9918477f07216 |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.