Triple
T10376006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APRR |
E244508
|
entity |
| Predicate | servesUserType |
P55187
|
FINISHED |
| Object | private motorists |
—
|
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: private motorists | Statement: [APRR, servesUserType, private motorists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesUserType Context triple: [APRR, servesUserType, private motorists]
-
A.
servesUsers
Indicates that an entity provides services, functionality, or benefits to one or more users.
-
B.
supportsUserType
chosen
Indicates that one entity is compatible with, or provides functionality for, a specified type or category of user.
-
C.
servesUsersFrom
Indicates that an entity provides services or resources to users originating from or associated with a specified source or location.
-
D.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
E.
servesUse
Indicates that one entity is used by or functions to serve the purpose or needs of 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98278e08190a4d3ff88b4039e49 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:02 p.m.