Triple
T26184602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Adelaide (L01) |
E654789
|
entity |
| Predicate | canOperateAircraftType |
P34747
|
FINISHED |
| Object | S-70B Seahawk |
—
|
NE NERFINISHED |
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: S-70B Seahawk | Statement: [HMAS Adelaide (L01), canOperateAircraftType, S-70B Seahawk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canOperateAircraftType Context triple: [HMAS Adelaide (L01), canOperateAircraftType, S-70B Seahawk]
-
A.
canOperateHelicopterType
chosen
Indicates that one entity has the ability, qualification, or authorization to operate or pilot a specified type of helicopter.
-
B.
aircraftTypeManaged
Indicates that one entity is responsible for managing or overseeing a particular type or category of aircraft.
-
C.
aircraftOperationType
Indicates the specific manner or purpose for which an aircraft is being operated (e.g., commercial, private, military, training).
-
D.
operatesAircraftFor
Indicates that one entity pilots or controls an aircraft on behalf of, or in service to, another entity.
-
E.
aircraftRoleRequired
Indicates that a specific operational role or function is required of an aircraft within a given context or mission.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c9d19748190b1e3405d56028876 |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:41 p.m.