Triple
T34211092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trajan's Bridge |
E877658
|
entity |
| Predicate | nearAncientSettlement |
P55312
|
FINISHED |
| Object | Drobeta |
—
|
NE NERFINISHED |
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: Drobeta | Statement: [Trajan's Bridge, nearAncientSettlement, Drobeta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearAncientSettlement Context triple: [Trajan's Bridge, nearAncientSettlement, Drobeta]
-
A.
nearAncientRegion
Indicates that one entity is located close to, or in the immediate vicinity of, a specified ancient geographical region.
-
B.
locatedInOrNearModernSettlement
Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
-
C.
hasNearbyAncientCity
chosen
Indicates that one entity is located close to another entity that is classified as an ancient city.
-
D.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
E.
nearbyRomanTown
Indicates that one location is geographically close to a town that existed during the Roman 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7105549b48190a0afbbb8c7c5bd0f |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.