Triple
T33004191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Hackney Carriage Drivers |
E844448
|
entity |
| Predicate | hasLiveryNumber |
P175895
|
FINISHED |
| Object | 104 |
—
|
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: 104 | Statement: [Worshipful Company of Hackney Carriage Drivers, hasLiveryNumber, 104]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveryNumber Context triple: [Worshipful Company of Hackney Carriage Drivers, hasLiveryNumber, 104]
-
A.
hasLivery
Indicates that one entity bears or displays the distinctive colors, markings, or branding (livery) associated with another entity.
-
B.
liveryNumber
chosen
Indicates the identifying number assigned to a vehicle or asset within a particular livery or fleet.
-
C.
hasLiveryStatus
Indicates that an entity has a particular livery condition or status applied to it, such as being painted, branded, or marked in a specific way.
-
D.
liveryType
Indicates the specific style, design, or branding scheme applied to an entity’s exterior appearance.
-
E.
liveryFeature
Indicates a characteristic or design element that is part of a specific livery or external appearance scheme.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 1, 2026, 1:23 a.m.