Triple
T37667473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 23 November 1939 |
E937858
|
entity |
| Predicate | RawalpindiCaptainDecision |
P182465
|
FINISHED |
| Object | refused to surrender |
—
|
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: refused to surrender | Statement: [Action of 23 November 1939, RawalpindiCaptainDecision, refused to surrender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RawalpindiCaptainDecision Context triple: [Action of 23 November 1939, RawalpindiCaptainDecision, refused to surrender]
-
A.
RawalpindiOperator
Indicates that an entity operates, manages, or runs a service, facility, or activity in Rawalpindi.
-
B.
captainDecision
chosen
Indicates that an individual, acting in the role of captain, makes or is responsible for a particular decision regarding others or a situation.
-
C.
RawalpindiOrigin
Indicates that an entity originates from, or has its source in, Rawalpindi.
-
D.
commanderPakistan
Indicates that one entity serves as the military or organizational commander of Pakistan.
-
E.
unitInvolvedPakistan
Indicates that a unit is involved in or associated with activities, operations, or events in Pakistan.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.