Triple
T26261197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Richmond railway station |
E656850
|
entity |
| Predicate | staffed |
P63143
|
FINISHED |
| Object | part-time |
—
|
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: part-time | Statement: [North Richmond railway station, staffed, part-time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: staffed Context triple: [North Richmond railway station, staffed, part-time]
-
A.
staffingLevel
chosen
Indicates the degree or adequacy of personnel assigned to perform a particular function, task, or operation.
-
B.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
C.
hasSupportStaff
Indicates that an entity is associated with one or more staff members who provide assistance or support services to it.
-
D.
attendedBy
Indicates that an event, place, or activity is participated in or visited by a particular person or group.
-
E.
employedThrough
Indicates that an entity holds a job or work position by means of, or via the arrangement of, another entity (such as an agency, contractor, or intermediary).
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dfea8bc819081f923c21b394a81 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:10 p.m.