Triple
T21755802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VanShare |
E537035
|
entity |
| Predicate | complementsServiceType |
P162
|
FINISHED |
| Object | traditional vanpool services |
—
|
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: traditional vanpool services | Statement: [VanShare, complementsServiceType, traditional vanpool services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complementsServiceType Context triple: [VanShare, complementsServiceType, traditional vanpool services]
-
A.
complements
chosen
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
B.
servicePatternComplement
Indicates that one service pattern functions as a complement to another, covering routes, times, or conditions that the other pattern does not.
-
C.
servicesType
Indicates the category or kind of services that one entity provides, uses, or is associated with in relation to another entity.
-
D.
offersServiceType
Indicates that one entity provides or makes available a specific type or category of service to another entity or the public.
-
E.
serviceFor
Indicates that one entity provides a service or performs functions on behalf 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8ea04c8190a8c4fa43b3f23935 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.