Triple
T13193254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heraclea at Latmus |
E314045
|
entity |
| Predicate | modernVicinity |
P33888
|
FINISHED |
| Object | Bafa Lake area |
—
|
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: Bafa Lake area | Statement: [Heraclea at Latmus, modernVicinity, Bafa Lake area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernVicinity Context triple: [Heraclea at Latmus, modernVicinity, Bafa Lake area]
-
A.
modernLocality
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
-
B.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
C.
nearModernAvenue
Indicates that one entity is located close to or in the vicinity of a modern avenue.
-
D.
nearModernSite
chosen
Indicates that one entity is located in close physical proximity to a site or location from the modern era.
-
E.
modernExistence
Indicates that an entity exists or is present in the contemporary or current time period.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:16 p.m.