Triple
T22686128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wewak region |
E560917
|
entity |
| Predicate | wasLinkedBy |
P141717
|
FINISHED |
| Object | Japanese supply routes in World War II |
—
|
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: Japanese supply routes in World War II | Statement: [Wewak region, wasLinkedBy, Japanese supply routes in World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLinkedBy Context triple: [Wewak region, wasLinkedBy, Japanese supply routes in World War II]
-
A.
canBeLinkedTo
Indicates that one entity has the potential or capability to be connected or associated with another entity.
-
B.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
-
C.
commonlyLinkedTo
Indicates that one entity is frequently or typically associated, connected, or co-occurring with another entity.
-
D.
associatedThrough
chosen
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
E.
linksFriendshipTo
Indicates a relationship that connects an entity to another entity with which it has a friendship.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178637bc08190a8dfb33b5f4249e5 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:12 p.m.