Triple
T37405293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Buses route 381 |
E929110
|
entity |
| Predicate | hasServiceProviderCategory |
P202453
|
FINISHED |
| Object | public transport |
—
|
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: public transport | Statement: [London Buses route 381, hasServiceProviderCategory, public transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceProviderCategory Context triple: [London Buses route 381, hasServiceProviderCategory, public transport]
-
A.
hasServiceProvider
Indicates that an entity is associated with or supported by a specific service provider.
-
B.
hasSupportCategory
Indicates that an entity is associated with a particular type or category of support it receives or provides.
-
C.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
D.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
E.
hasServiceFrom
Indicates that one entity receives or benefits from a service provided by another entity.
- F. None of above. chosen
Provenance (4 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
| PDg | Predicate description generation | batch_6a00809836f081908de40255d4f4d525 |
completed | May 10, 2026, 12:56 p.m. |
Created at: May 3, 2026, 4:16 p.m.