Triple
T4931911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macclesfield Canal |
E110714
|
entity |
| Predicate | primaryCargoHistorical |
P5941
|
FINISHED |
| Object | coal |
—
|
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: coal | Statement: [Macclesfield Canal, primaryCargoHistorical, coal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCargoHistorical Context triple: [Macclesfield Canal, primaryCargoHistorical, coal]
-
A.
historicallyStoredGoods
Indicates that an entity has previously stored certain goods at some time in the past.
-
B.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
C.
historicTradeRole
Indicates that an entity historically functioned as a significant participant or hub in trade or commercial exchange.
-
D.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
E.
mainCargo
chosen
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7063c57c8190a5a6fb3586238d35 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.