Triple
T2329435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IJN battleship Yamashiro |
E48365
|
entity |
| Predicate | aircraftFacilities |
P13763
|
FINISHED |
| Object | catapult for floatplanes |
—
|
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: catapult for floatplanes | Statement: [IJN battleship Yamashiro, aircraftFacilities, catapult for floatplanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftFacilities Context triple: [IJN battleship Yamashiro, aircraftFacilities, catapult for floatplanes]
-
A.
aircraftFacility
chosen
Indicates that a facility is designed, equipped, or used to support the operation, maintenance, or accommodation of aircraft.
-
B.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another entity.
-
C.
locationOnAircraft
Indicates that one entity is physically situated on or within an aircraft.
-
D.
airSupport
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
-
E.
flightDeckType
Indicates the specific configuration or design type of a vehicle’s flight deck (cockpit/control area).
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:50 p.m.