Triple
T27602589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | submarine tender Takasaki |
E700089
|
entity |
| Predicate | navalRoleAfterConversion |
P164509
|
FINISHED |
| Object | aircraft carrier |
—
|
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: aircraft carrier | Statement: [submarine tender Takasaki, navalRoleAfterConversion, aircraft carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalRoleAfterConversion Context triple: [submarine tender Takasaki, navalRoleAfterConversion, aircraft carrier]
-
A.
roleAfterNavalService
Indicates the position or role an individual assumes following the completion of their naval service.
-
B.
hasNavalRole
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
-
C.
successorRoleShip
Indicates that one role succeeds or takes over from another role in a sequence or hierarchy.
-
D.
navalEngagementRole
Indicates the specific function or duty an entity performs within a naval engagement or maritime combat operation.
-
E.
navalTacticRole
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
- F. None of above. chosen
Provenance (4 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_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 2:08 p.m.