Triple
T3615512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranikot Fort |
E76590
|
entity |
| Predicate | approximatePerimeter |
P33371
|
FINISHED |
| Object | about 32 kilometers |
—
|
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: about 32 kilometers | Statement: [Ranikot Fort, approximatePerimeter, about 32 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePerimeter Context triple: [Ranikot Fort, approximatePerimeter, about 32 kilometers]
-
A.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
B.
areaApprox
Indicates that one entity’s area is approximately equal to the area of another entity.
-
C.
perimeter
chosen
Indicates the total length around the boundary of a two-dimensional shape or region.
-
D.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
E.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27b5e008190a72a8dab7d736e64 |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.