Triple
T27602599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | submarine tender Takasaki |
E700089
|
entity |
| Predicate | hasShipClassAfterConversion |
P170379
|
FINISHED |
| Object | Zuiho-class aircraft carrier |
—
|
NE NERFINISHED |
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: Zuiho-class aircraft carrier | Statement: [submarine tender Takasaki, hasShipClassAfterConversion, Zuiho-class aircraft carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShipClassAfterConversion Context triple: [submarine tender Takasaki, hasShipClassAfterConversion, Zuiho-class aircraft carrier]
-
A.
hasShipInClass
Indicates that an entity possesses or includes at least one ship that belongs to a specified ship class.
-
B.
hasShipCategory
Indicates that an entity is associated with or classified under a particular category or type of ship.
-
C.
hasShipPrefix
Indicates that a ship is associated with or identified by a specific prefix in its name or designation.
-
D.
hasShip
Indicates that one entity possesses, owns, or is equipped with a ship.
-
E.
hasShipTypeCharacteristic
Indicates that a ship possesses a specific characteristic or property related to its type.
- 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_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 27, 2026, 2:08 p.m.