Triple
T11869391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuihō-class aircraft carrier |
E282366
|
entity |
| Predicate | hullOrigin |
P101359
|
FINISHED |
| Object | converted merchant-type hull |
—
|
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: converted merchant-type hull | Statement: [Zuihō-class aircraft carrier, hullOrigin, converted merchant-type hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullOrigin Context triple: [Zuihō-class aircraft carrier, hullOrigin, converted merchant-type hull]
-
A.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
B.
hullLayout
Indicates how the structural arrangement or configuration of a vessel’s hull is organized or laid out in relation to its components.
-
C.
usedHullNumberSystem
Indicates that an entity employed a hull numbering system to identify or classify ships or vessels.
-
D.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
E.
hullColor
Indicates the color attribute assigned to the outer surface (hull) of an object, typically a vehicle or vessel.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73c04e4819084c0b2ff8e5d2f04 |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2589f0c8190ad82ff11acabae93 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43db84481909218ffe69be6482c |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.