Triple
T9206709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consolidated Aircraft |
E220998
|
entity |
| Predicate | PBYCatalinaRole |
P2860
|
FINISHED |
| Object | maritime patrol and search-and-rescue |
—
|
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: maritime patrol and search-and-rescue | Statement: [Consolidated Aircraft, PBYCatalinaRole, maritime patrol and search-and-rescue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PBYCatalinaRole Context triple: [Consolidated Aircraft, PBYCatalinaRole, maritime patrol and search-and-rescue]
-
A.
PC-6Role
Indicates that an entity participates in or is assigned a specific role within a PC-6 (Pilatus PC-6 aircraft)–related context or activity.
-
B.
basedAircraftRole
Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
-
C.
notableAircraftRole
Indicates that an aircraft is notably associated with performing a particular role or function.
-
D.
usedOnAircraftRole
Indicates that something is employed or applied in the context of a specific role or function on an aircraft.
-
E.
primaryAircraftRole
chosen
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
- 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9b0b6788190908bee67a0c5d48f |
completed | April 1, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:26 p.m.