Triple
T4035838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 26 frigate |
E83824
|
entity |
| Predicate | hangarCapacity |
P22186
|
FINISHED |
| Object | one Merlin-size helicopter |
—
|
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: one Merlin-size helicopter | Statement: [Type 26 frigate, hangarCapacity, one Merlin-size helicopter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hangarCapacity Context triple: [Type 26 frigate, hangarCapacity, one Merlin-size helicopter]
-
A.
hasHangarCount
Indicates the number of hangars associated with or contained by an entity.
-
B.
hasHangars
chosen
Indicates that one entity possesses or contains hangars used for housing aircraft or similar vehicles.
-
C.
aircraftCapacity
Indicates the maximum number of passengers or amount of load that an aircraft is designed or allowed to carry.
-
D.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
E.
paratroopCapacity
Indicates the maximum number of paratroopers or amount of airborne troops that something (typically a vehicle or vessel) is capable of carrying or deploying.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb132f6c8190937acd35a6a5a9e4 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.