Triple
T5728786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trafford Park railway station |
E126330
|
entity |
| Predicate | hasStaffing |
P63143
|
FINISHED |
| Object | unstaffed |
—
|
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: unstaffed | Statement: [Trafford Park railway station, hasStaffing, unstaffed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStaffing Context triple: [Trafford Park railway station, hasStaffing, unstaffed]
-
A.
staffingLevel
chosen
Indicates the degree or adequacy of personnel assigned to perform a particular function, task, or operation.
-
B.
hasStaffedHours
Indicates that specific hours or time periods are assigned during which staff are present and available.
-
C.
hasGeneralStaff
Indicates that an entity has, is associated with, or is served by a general staff body responsible for overall strategic or administrative functions.
-
D.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
E.
hasWorkforceType
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.