Triple
T17703736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanov-on-Murman |
E441375
|
entity |
| Predicate | portFor |
P92400
|
FINISHED |
| Object | Allied supplies in World War I |
—
|
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: Allied supplies in World War I | Statement: [Romanov-on-Murman, portFor, Allied supplies in World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portFor Context triple: [Romanov-on-Murman, portFor, Allied supplies in World War I]
-
A.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
B.
isPortFor
chosen
Indicates that one entity serves as a port, interface, or connection point for another entity.
-
C.
port
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
-
D.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
-
E.
portAlsoKnownAs
Indicates that a port is referred to by an alternative name or alias.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729528b88190bd8a104f6f6d4e69 |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:05 a.m.