Triple
T26486671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taiho-class aircraft carrier |
E664840
|
entity |
| Predicate | hasArmoredFlightDeck |
P34590
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Taiho-class aircraft carrier, hasArmoredFlightDeck, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArmoredFlightDeck Context triple: [Taiho-class aircraft carrier, hasArmoredFlightDeck, true]
-
A.
hasArmedWing
Indicates that an entity maintains, controls, or is associated with an organized armed or military wing.
-
B.
armamentAsCarrier
Indicates that one entity serves as a carrier or delivery platform for another entity used as an armament or weapon.
-
C.
flightDeckType
Indicates the specific configuration or design type of a vehicle’s flight deck (cockpit/control area).
-
D.
hasAircraftCarrier
Indicates that one entity possesses, operates, or includes an aircraft carrier as part of its assets or resources.
-
E.
flightDeckFeature
chosen
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 12:31 a.m.