Triple
T30403930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryusei |
E773426
|
entity |
| Predicate | usedOnAircraftCarrier |
P32564
|
FINISHED |
| Object | Taiho |
—
|
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: Taiho | Statement: [Ryusei, usedOnAircraftCarrier, Taiho]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnAircraftCarrier Context triple: [Ryusei, usedOnAircraftCarrier, Taiho]
-
A.
hasAircraftCarrier
Indicates that one entity possesses, operates, or includes an aircraft carrier as part of its assets or resources.
-
B.
aircraftCarrierOperatedFrom
Indicates that an aircraft carrier conducts its operations from, or is based at, a particular location or facility.
-
C.
usesCarrierAircraft
chosen
Indicates that one entity employs or operates aircraft that are designed to be launched from and recovered by an aircraft carrier.
-
D.
aircraftCarrierInvolved
Indicates that an aircraft carrier participates in, is present at, or is otherwise directly involved in the specified event or situation.
-
E.
aircraftCarrierDepicted
Indicates that an aircraft carrier is visually represented or shown in the associated media or depiction.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6861c95e88190a5f3a4a6c952692a |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:03 p.m.