Triple
T5347063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RADIUS |
E124082
|
entity |
| Predicate | clientTypicallyIs |
P41733
|
FINISHED |
| Object | network access server |
—
|
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: network access server | Statement: [RADIUS, clientTypicallyIs, network access server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientTypicallyIs Context triple: [RADIUS, clientTypicallyIs, network access server]
-
A.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
B.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
C.
clientFor
Indicates that one entity acts as a client that uses the services, resources, or interface provided by another entity.
-
D.
primaryClient
Indicates that one entity serves as the main or most important client associated with another entity.
-
E.
typicalProfile
chosen
Indicates that an entity represents the standard or most representative profile or pattern for 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_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.