Triple
T28590075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Liao |
E723615
|
entity |
| Predicate | maintainedSilkRoadRoutes |
P174374
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Western Liao, maintainedSilkRoadRoutes, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedSilkRoadRoutes Context triple: [Western Liao, maintainedSilkRoadRoutes, Yes]
-
A.
includesTradeRoute
Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
-
B.
numberOfRoutes
Indicates the total count of distinct routes or paths associated with a given entity or between specified entities.
-
C.
operatedRoutes
Indicates that an agent (such as a company or organization) runs or manages specific routes, typically providing services along those paths.
-
D.
connectsInlandRoutesTo
Indicates that one entity serves as a link or junction that enables inland transportation routes to reach or connect with another entity.
-
E.
controlledPilgrimageRoutesTo
Indicates that one entity had authority over and managed access to the pilgrimage routes leading to another entity.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 28, 2026, 4:19 a.m.