Triple
T25265286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Struma |
E633412
|
entity |
| Predicate | routeContext |
P158075
|
FINISHED |
| Object | illegal immigration to Mandatory Palestine |
—
|
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: illegal immigration to Mandatory Palestine | Statement: [Struma, routeContext, illegal immigration to Mandatory Palestine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeContext Context triple: [Struma, routeContext, illegal immigration to Mandatory Palestine]
-
A.
routeSystem
Indicates a transportation or communication network framework within which specific routes are organized, defined, or managed.
-
B.
routeOrigin
Indicates the starting point or source location from which a route begins.
-
C.
routeTypeAccessed
Indicates that a particular type of route has been accessed or used in some context.
-
D.
routeSegment
Indicates a specific portion of a larger route that directly connects two points or locations within that route.
-
E.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4839787908190a5fc04739139cee8 |
completed | May 1, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 1:14 p.m.