Triple
T26522452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montevideo Maru |
E669993
|
entity |
| Predicate | requisitionedDuring |
P180695
|
FINISHED |
| Object | World War II |
—
|
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: World War II | Statement: [Montevideo Maru, requisitionedDuring, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requisitionedDuring Context triple: [Montevideo Maru, requisitionedDuring, World War II]
-
A.
requisitionedBy
Indicates that something has been formally requested or claimed for official use by a particular agent or authority.
-
B.
demandedDuring
Indicates that one entity formally requested or required something from another entity within a specific time period or event.
-
C.
requisitionDate
Indicates the date on which a formal request or requisition for goods, services, or resources was created or submitted.
-
D.
shipsRequisitionedBy
Indicates that certain ships have been formally taken over or commandeered by a specified party or authority.
-
E.
requestedFor
Indicates that one entity has made a request on behalf of, or targeting, another entity as the intended recipient or subject of the request.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: April 27, 2026, 1:29 a.m.