Triple
T26522455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montevideo Maru |
E669993
|
entity |
| Predicate | routePrewar |
P153000
|
FINISHED |
| Object | Japan–South America route |
—
|
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: Japan–South America route | Statement: [Montevideo Maru, routePrewar, Japan–South America route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routePrewar Context triple: [Montevideo Maru, routePrewar, Japan–South America route]
-
A.
preWarServiceArea
Indicates the geographic area or jurisdiction in which an entity operated or provided service before a specified war or conflict.
-
B.
routeOf
chosen
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
C.
prewarStatus
Indicates the condition, role, or circumstances of an entity as they existed before a specific war or armed conflict.
-
D.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
E.
postWarLocation
Indicates the place where an entity is located or based after a war or major conflict has ended.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613c35b5481909ef85d87d1604be9 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:29 a.m.