Triple
T8948000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borysthenes |
E213269
|
entity |
| Predicate | roleInAntiquity |
P46173
|
FINISHED |
| Object | major trade route |
—
|
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: major trade route | Statement: [Borysthenes, roleInAntiquity, major trade route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAntiquity Context triple: [Borysthenes, roleInAntiquity, major trade route]
-
A.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
B.
politicalStatusInAntiquity
Indicates the political condition or classification an entity held during ancient times, such as its form of governance, sovereignty, or dependency.
-
C.
reputationInAntiquity
chosen
Indicates the reputation or standing an entity had during ancient times.
-
D.
roleInMonarchyPeriod
Indicates that an entity held a specific role or position during a defined period of a monarchy.
-
E.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6709c7a48190ab503083a1d6a29f |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.