Triple
T28444525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OzEmail |
E715802
|
entity |
| Predicate | offeredAccessMethod |
P74649
|
FINISHED |
| Object | dial-up modem |
—
|
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 modem | Statement: [OzEmail, offeredAccessMethod, dial-up modem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredAccessMethod Context triple: [OzEmail, offeredAccessMethod, dial-up modem]
-
A.
hasAccessMethod
Indicates that one entity uses or is associated with a particular method or mechanism for accessing another entity or resource.
-
B.
offersAccessVia
chosen
Indicates that one entity provides a means or channel through which another entity can be accessed or utilized.
-
C.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
D.
accessionMethod
Indicates the process or means by which something is acquired, obtained, or added to a collection or system.
-
E.
offersAccess
Indicates that one entity provides another entity with the ability or permission to use, enter, or interact with a resource, service, or location.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 28, 2026, 1:48 a.m.