Triple
T11869406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuihō-class aircraft carrier |
E282366
|
entity |
| Predicate | hasArrestingGear |
P101360
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Zuihō-class aircraft carrier, hasArrestingGear, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArrestingGear Context triple: [Zuihō-class aircraft carrier, hasArrestingGear, yes]
-
A.
hasRunningGear
Indicates that an entity is equipped with or possesses running gear, such as the mechanical components that enable movement or operation.
-
B.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
C.
equippedFor
Indicates that one entity is suitably provided with the necessary tools, features, or capabilities to perform a particular function or handle a specific situation for another entity or purpose.
-
D.
usesArmoredVehicle
Indicates that an entity employs or operates an armored vehicle in performing an action or fulfilling a role.
-
E.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
- 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.