Triple
T9594337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Daring (D32) |
E231492
|
entity |
| Predicate | helicopterFacility |
P13763
|
FINISHED |
| Object | flight deck |
—
|
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: flight deck | Statement: [HMS Daring (D32), helicopterFacility, flight deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helicopterFacility Context triple: [HMS Daring (D32), helicopterFacility, flight deck]
-
A.
hasHeliport
Indicates that an entity possesses or is equipped with a heliport facility for helicopter landing and takeoff.
-
B.
isHelicopterOf
Indicates that one entity is a helicopter that belongs to, is operated by, or is otherwise associated with another entity.
-
C.
aircraftFacility
chosen
Indicates that a facility is designed, equipped, or used to support the operation, maintenance, or accommodation of aircraft.
-
D.
hasHelicopterTrainingRole
Indicates that an entity holds a role or position specifically related to the training or instruction of helicopter operations.
-
E.
isHelicopterOnly
Indicates that the subject is restricted to or designated exclusively for use by helicopters.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a14fd308190beb8fda5a9e912c7 |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.