Triple
T29735434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akhurian River gorge |
E752444
|
entity |
| Predicate | hasNearbyStructureType |
P124983
|
FINISHED |
| Object | medieval bridges |
—
|
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: medieval bridges | Statement: [Akhurian River gorge, hasNearbyStructureType, medieval bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyStructureType Context triple: [Akhurian River gorge, hasNearbyStructureType, medieval bridges]
-
A.
hasNearbyInfrastructureType
chosen
Indicates that an entity is located close to infrastructure of a specified type.
-
B.
hasNearbyEntityType
Indicates that an entity has at least one other entity of a specified type located within a defined nearby spatial or contextual range.
-
C.
hasNearbyLandscapeType
Indicates that one entity is located close to, or in the vicinity of, a particular type of landscape.
-
D.
hasNearbyCivicBuilding
Indicates that one entity is located close to, or in the immediate vicinity of, a civic building such as a government, public service, or community facility.
-
E.
hasNearbySiteType
Indicates that one entity has another entity of a specified site type located in its close physical vicinity.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 28, 2026, 7:45 p.m.