Triple
T4624453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Canal of China |
E101060
|
entity |
| Predicate | primaryHistoricalFunction |
P2715
|
FINISHED |
| Object | transport of grain |
—
|
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: transport of grain | Statement: [Grand Canal of China, primaryHistoricalFunction, transport of grain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHistoricalFunction Context triple: [Grand Canal of China, primaryHistoricalFunction, transport of grain]
-
A.
historicalFunction
chosen
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
B.
primaryFunctionInPrehistory
Indicates the main role or use an entity had during prehistoric times, before written records.
-
C.
historicalCharacteristic
Indicates that an entity possesses a trait, feature, or quality that is rooted in or defined by its history or past events.
-
D.
historicalFocus
Indicates that something is primarily concerned with, centered on, or devoted to a particular historical period, event, or theme.
-
E.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a06d6248190a613be9784dd1ef4 |
completed | March 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.