Triple
T5347051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RADIUS |
E124082
|
entity |
| Predicate | initiallyDesignedFor |
P11902
|
FINISHED |
| Object | dial-up remote access |
—
|
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: dial-up remote access | Statement: [RADIUS, initiallyDesignedFor, dial-up remote access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyDesignedFor Context triple: [RADIUS, initiallyDesignedFor, dial-up remote access]
-
A.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
B.
originallyDevelopedFor
chosen
Indicates that something was first created, designed, or produced with the primary purpose of serving a particular use, user group, context, or application.
-
C.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
D.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
E.
firstWidelyUsedFor
Indicates that something was the earliest instance to be broadly adopted or commonly used for a particular purpose or application.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ede7c481908347d557aa4d19ad |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.