Triple
T13327338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ankyra |
E317473
|
entity |
| Predicate | wasOnTradeRoute |
P13518
|
FINISHED |
| Object | routes between East and West Anatolia |
—
|
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: routes between East and West Anatolia | Statement: [Ankyra, wasOnTradeRoute, routes between East and West Anatolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOnTradeRoute Context triple: [Ankyra, wasOnTradeRoute, routes between East and West Anatolia]
-
A.
includesTradeRoute
Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
-
B.
hadTradingPostNetwork
Indicates that an entity maintained or controlled a network of trading posts used for commercial exchange or trade activities.
-
C.
usedForTradeBetween
Indicates that something serves as a medium, instrument, or basis for trade or exchange between two or more parties.
-
D.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
E.
wasCrossroadsOf
chosen
Indicates that a place served as a central junction or meeting point where multiple routes, paths, or influences converged.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.