Triple
T31902911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karachi Agreement of 1949 |
E814470
|
entity |
| Predicate | mapScaleUsed |
P62522
|
FINISHED |
| Object | 1:1,000,000 |
—
|
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: 1:1,000,000 | Statement: [Karachi Agreement of 1949, mapScaleUsed, 1:1,000,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapScaleUsed Context triple: [Karachi Agreement of 1949, mapScaleUsed, 1:1,000,000]
-
A.
mapScale
chosen
Indicates the ratio between distances on a map and the corresponding actual distances in the real world.
-
B.
mapScaleCategory
Indicates the classification of a map based on its scale range or level of detail.
-
C.
distanceScaleUse
Indicates that one entity uses or applies the distance scale defined or provided by another entity.
-
D.
areaScale
Indicates a proportional relationship where one area value is a scaled (enlarged or reduced) version of another by a specific factor.
-
E.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1b18c30819098ac3103f54ad310 |
completed | May 3, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, midnight