Triple
T37667467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 23 November 1939 |
E937858
|
entity |
| Predicate | RawalpindiOrigin |
P189117
|
FINISHED |
| Object | converted passenger liner |
—
|
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: converted passenger liner | Statement: [Action of 23 November 1939, RawalpindiOrigin, converted passenger liner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RawalpindiOrigin Context triple: [Action of 23 November 1939, RawalpindiOrigin, converted passenger liner]
-
A.
entryPointFromPakistan
Indicates that something serves as a point of entry originating from Pakistan.
-
B.
distanceFrom Peshawar
Indicates the spatial distance between a given location or entity and the city of Peshawar.
-
C.
capitalOfOrigin
Indicates that one entity is the capital city associated with the origin (such as birthplace, founding place, or source location) of another entity.
-
D.
distanceFromRawalpindiCityCenter
Indicates the measured distance between a given location and the central point of Rawalpindi city.
-
E.
distanceFromIslamabad
Indicates the spatial distance between a given location and the city of Islamabad.
- F. None of above. chosen
Provenance (4 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:18 p.m.