Triple
T2045289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supermarine Seafang |
E45435
|
entity |
| Predicate | navalFeatures |
P36018
|
FINISHED |
| Object | arrestor hook |
—
|
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: arrestor hook | Statement: [Supermarine Seafang, navalFeatures, arrestor hook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalFeatures Context triple: [Supermarine Seafang, navalFeatures, arrestor hook]
-
A.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
B.
navalForceComposition
Indicates the makeup and distribution of different types of naval units or vessels within a particular naval force.
-
C.
hasNavalFacility
Indicates that one entity possesses, hosts, or contains a naval facility (such as a naval base, port, or installation) associated with it.
-
D.
navalAccess
Indicates that one entity has the right or ability to use another entity’s naval facilities, waters, or maritime routes for military or strategic purposes.
-
E.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abbc2b07d48190ba9d67353167b472 |
completed | March 7, 2026, 5:48 a.m. |
Created at: March 4, 2026, 7:39 p.m.