Triple
T33490687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamistra |
E857728
|
entity |
| Predicate | nearAncientRoad |
P115769
|
FINISHED |
| Object | route between Tarsus and Antioch |
—
|
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: route between Tarsus and Antioch | Statement: [Mamistra, nearAncientRoad, route between Tarsus and Antioch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearAncientRoad Context triple: [Mamistra, nearAncientRoad, route between Tarsus and Antioch]
-
A.
nearAncientRegion
Indicates that one entity is located close to, or in the immediate vicinity of, a specified ancient geographical region.
-
B.
nearHistoricalRoute
chosen
Indicates that one entity is located close to a historically significant route or pathway.
-
C.
nearScenicRoute
Indicates that one entity is located close to a route or path that is considered scenic or visually appealing.
-
D.
nearJunctionOf
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
-
E.
nearModernAvenue
Indicates that one entity is located close to or in the vicinity of a modern avenue.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e565dc0481908b03d4d0d8ec7d5d |
completed | May 3, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3db74c081909a991309d835d477 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.