Triple
T31903321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LeT |
E814479
|
entity |
| Predicate | hasTrainingCampsInPast |
P46335
|
FINISHED |
| Object | Pakistan-administered Kashmir |
—
|
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: Pakistan-administered Kashmir | Statement: [LeT, hasTrainingCampsInPast, Pakistan-administered Kashmir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingCampsInPast Context triple: [LeT, hasTrainingCampsInPast, Pakistan-administered Kashmir]
-
A.
hasTrainingSessions
Indicates that an entity conducts, provides, or is associated with one or more training sessions for another entity.
-
B.
trainingCamps
chosen
Indicates that one entity organizes, hosts, or is associated with training camps for another entity or group.
-
C.
hasTrainedAt
Indicates that an entity has received training, education, or instruction at a specified place or institution.
-
D.
hasTrainingTrack
Indicates that an entity is associated with or assigned to a specific training track or program.
-
E.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
- 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_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 1, 2026, midnight