Triple
T21788799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Lawyer Referral Service |
E537911
|
entity |
| Predicate | offersAccessMethod |
P74649
|
FINISHED |
| Object | telephone |
—
|
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: telephone | Statement: [Virginia Lawyer Referral Service, offersAccessMethod, telephone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersAccessMethod Context triple: [Virginia Lawyer Referral Service, offersAccessMethod, telephone]
-
A.
offersAccessVia
chosen
Indicates that one entity provides a means or channel through which another entity can be accessed or utilized.
-
B.
offersAccess
Indicates that one entity provides another entity with the ability or permission to use, enter, or interact with a resource, service, or location.
-
C.
offersConnectionTo
Indicates that one entity provides or enables access, linkage, or connectivity to another entity.
-
D.
offersModality
Indicates that one entity provides or supports a particular mode, method, or form in which something can be experienced, delivered, or performed.
-
E.
offersProcedure
Indicates that one entity provides or makes available a specific procedure to 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621dfa3c8190921bfccbff7331f2 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.