Triple
T16983793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian cruiser Varyag |
E412008
|
entity |
| Predicate | serviceAs |
P18496
|
FINISHED |
| Object | training ship in Imperial Japanese Navy |
—
|
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: training ship in Imperial Japanese Navy | Statement: [Russian cruiser Varyag, serviceAs, training ship in Imperial Japanese Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceAs Context triple: [Russian cruiser Varyag, serviceAs, training ship in Imperial Japanese Navy]
-
A.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
B.
serviceIs
Indicates that one entity functions as a service of a specified type or category in relation to another entity.
-
C.
serviceIn
chosen
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
D.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
E.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18a0bf881908c449f499eb86495 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.