Triple
T27602588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | submarine tender Takasaki |
E700089
|
entity |
| Predicate | navalRoleBeforeConversion |
P101660
|
FINISHED |
| Object | submarine support ship |
—
|
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: submarine support ship | Statement: [submarine tender Takasaki, navalRoleBeforeConversion, submarine support ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalRoleBeforeConversion Context triple: [submarine tender Takasaki, navalRoleBeforeConversion, submarine support ship]
-
A.
roleBeforeNavalService
Indicates that one role or position held by an individual occurred prior to that individual's naval service.
-
B.
hasNavalRole
chosen
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
-
C.
roleAfterNavalService
Indicates the position or role an individual assumes following the completion of their naval service.
-
D.
shipHistoricalRole
Indicates the historical function or significance a ship had, such as its role in events, conflicts, or periods of service.
-
E.
navalEngagementRole
Indicates the specific function or duty an entity performs within a naval engagement or maritime combat operation.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 2:08 p.m.