Triple
T18664783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFB Shearwater |
E456296
|
entity |
| Predicate | hasMaritimeHelicopterSquadrons |
P132201
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [CFB Shearwater, hasMaritimeHelicopterSquadrons, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeHelicopterSquadrons Context triple: [CFB Shearwater, hasMaritimeHelicopterSquadrons, true]
-
A.
aircraftMaritimePatrol
Indicates that an aircraft is engaged in maritime patrol operations, monitoring and surveying sea areas for security, reconnaissance, or search-and-rescue purposes.
-
B.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
C.
squadronFlagshipOf
Indicates that one entity serves as the primary or lead flagship vessel of a particular squadron.
-
D.
hasAmphibiousCapability
Indicates that an entity possesses the ability to operate effectively in both water and land environments.
-
E.
airborneForces
Indicates that military forces are deployed, transported, or operating via aircraft, typically inserted from the air into an operational area.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5508d2d588190a468bd7b205d2057 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.