Triple
T2992691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halifax-class frigate |
E80992
|
entity |
| Predicate | airCapability |
P44564
|
FINISHED |
| Object | embarks maritime 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: embarks maritime helicopter | Statement: [Halifax-class frigate, airCapability, embarks maritime helicopter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airCapability Context triple: [Halifax-class frigate, airCapability, embarks maritime helicopter]
-
A.
landingCapability
Indicates the ability or suitability of an entity (e.g., a vehicle or system) to perform a landing under specified conditions.
-
B.
flightAbility
Indicates the capability or potential of an entity to fly or engage in powered or unpowered aerial movement.
-
C.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
D.
aircraft
Indicates that an entity is an aircraft or functions in the role of an aircraft in the described context.
-
E.
airSupport
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99e12c5c8190af7cc20e4c48bf45 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:59 p.m.