Triple
T11300300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livonia Marketplace |
E267565
|
entity |
| Predicate | hasCustomerAccess |
P1017
|
FINISHED |
| Object | road transportation |
—
|
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: road transportation | Statement: [Livonia Marketplace, hasCustomerAccess, road transportation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerAccess Context triple: [Livonia Marketplace, hasCustomerAccess, road transportation]
-
A.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
B.
hasAccessTo
chosen
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
C.
hasDisabledAccess
Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
-
D.
hasCustomers
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
E.
hasCustomerServices
Indicates that an entity provides or is associated with one or more customer service functions or offerings.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a4aad4819097384e1b591be2e3 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.