Triple
T4253553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Punjab, Pakistan |
E95914
|
entity |
| Predicate | hasMovementFor |
P44014
|
FINISHED |
| Object | separate province status |
—
|
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: separate province status | Statement: [Southern Punjab, Pakistan, hasMovementFor, separate province status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMovementFor Context triple: [Southern Punjab, Pakistan, hasMovementFor, separate province status]
-
A.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
B.
hasImportantMovement
chosen
Indicates that an entity is associated with a movement (e.g., social, artistic, political) that is considered significant or influential.
-
C.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
-
D.
hasMovementStructure
Indicates that one entity possesses or is characterized by a particular structure or pattern of movement.
-
E.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ebe6fbc8190a89269b478b3f435 |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.