Triple
T35103564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weston Village |
E1013085
|
entity |
| Predicate | hasUPExpressService |
P182523
|
FINISHED |
| Object | Union Pearson Express |
—
|
NE NERFINISHED |
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: Union Pearson Express | Statement: [Weston Village, hasUPExpressService, Union Pearson Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUPExpressService Context triple: [Weston Village, hasUPExpressService, Union Pearson Express]
-
A.
hasLimitedExpressBrand
Indicates that an entity possesses or is associated with a Limited Express brand designation or service.
-
B.
primaryExpressService
Indicates that an entity provides or is associated with the main, prioritized express-level service in a given context.
-
C.
servesCarrier
Indicates that one entity provides carrier services or functions as a carrier on behalf of another entity.
-
D.
hasPostalServiceThrough
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
-
E.
hasCenterExpressTracks
Indicates that the subject location or facility contains express railway tracks running through its central area or core.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.