Triple
T34569260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardwick railway depot |
E887576
|
entity |
| Predicate | hasDepotCode |
P199114
|
FINISHED |
| Object | AK |
—
|
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: AK | Statement: [Ardwick railway depot, hasDepotCode, AK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepotCode Context triple: [Ardwick railway depot, hasDepotCode, AK]
-
A.
hasAdjacentDepot
Indicates that one entity has a depot located directly next to or adjoining it.
-
B.
hasDepotBuilding
Indicates that an entity possesses, includes, or is associated with a depot building as part of its facilities or infrastructure.
-
C.
depotFor
Indicates that one entity serves as a storage or distribution center location dedicated to supporting or supplying another entity.
-
D.
hasStationCode
Indicates that an entity is associated with a specific station identification code.
-
E.
hasPortCode
Indicates that an entity (such as a port or terminal) is associated with a specific standardized port code identifier.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
| PDg | Predicate description generation | batch_69ff1f3ee3588190a857d1504c93be8b |
completed | May 9, 2026, 11:49 a.m. |
Created at: May 1, 2026, 2:02 a.m.