Triple
T32053952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy frigates |
E818564
|
entity |
| Predicate | typicallyEmbark |
P44565
|
FINISHED |
| Object | anti-submarine warfare 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: anti-submarine warfare helicopter | Statement: [Royal Navy frigates, typicallyEmbark, anti-submarine warfare helicopter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyEmbark Context triple: [Royal Navy frigates, typicallyEmbark, anti-submarine warfare helicopter]
-
A.
typicallySpared
Indicates that an entity is usually not affected by, excluded from, or left untouched by a particular action, process, or condition.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
designedToEmbark
chosen
Indicates that something is created or configured with the specific purpose of beginning or initiating a journey, process, or undertaking.
-
D.
typicalGoing
Indicates that an entity is engaged in or undergoing a normal, expected instance of going or movement from one place to another.
-
E.
typicalExpeditionMode
Indicates the usual or most common mode or method by which an expedition is conducted.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:21 a.m.