Triple
T31902893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karachi Agreement of 1949 |
E814470
|
entity |
| Predicate | lineStartPoint |
P389
|
FINISHED |
| Object | Manawar in Jammu region |
—
|
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: Manawar in Jammu region | Statement: [Karachi Agreement of 1949, lineStartPoint, Manawar in Jammu region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineStartPoint Context triple: [Karachi Agreement of 1949, lineStartPoint, Manawar in Jammu region]
-
A.
startPoint
chosen
Indicates the initial location or position from which an object, path, or action begins.
-
B.
linePositioning
Indicates how one line is spatially arranged or oriented in relation to another line.
-
C.
linePositioning
Indicates the relative arrangement or alignment of elements along a line or linear sequence.
-
D.
startPointLocatedIn
Indicates that the starting point of something is geographically or spatially located within a specified area or region.
-
E.
lineSectionOpenedWith
Indicates that a specific section of a line (such as a route, track, or service line) has been officially opened or put into operation by a particular action or event.
- 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