Triple
T32019137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabran (historical city) |
E817629
|
entity |
| Predicate | presentDaySettlementNearby |
P138521
|
FINISHED |
| Object | Shabran (modern town) |
—
|
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: Shabran (modern town) | Statement: [Shabran (historical city), presentDaySettlementNearby, Shabran (modern town)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDaySettlementNearby Context triple: [Shabran (historical city), presentDaySettlementNearby, Shabran (modern town)]
-
A.
nearbyCurrent
Indicates that one entity is located close to another entity at the present moment or in the current context.
-
B.
nearbySettlements
chosen
Indicates that one settlement is located close to another settlement in geographic space.
-
C.
presentDayNear
Indicates that one entity is located a short distance from another in the present time or current context.
-
D.
nearbySettlementStatus
Indicates whether a settlement is located close enough to another reference point or area to be considered nearby.
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 12:16 a.m.