Triple
T31463277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deaf Australians |
E802660
|
entity |
| Predicate | accessService |
P143389
|
FINISHED |
| Object | Auslan–English interpreting |
—
|
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: Auslan–English interpreting | Statement: [Deaf Australians, accessService, Auslan–English interpreting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessService Context triple: [Deaf Australians, accessService, Auslan–English interpreting]
-
A.
serviceAccess
chosen
Indicates that one entity is permitted to use, reach, or interact with a particular service provided by another entity.
-
B.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
C.
accessProvides
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
-
D.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
E.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 30, 2026, 9:21 p.m.