Triple
T36626848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buccaneer S.1 |
E904197
|
entity |
| Predicate | takeoffAndLandingAid |
P186100
|
FINISHED |
| Object | boundary layer control for carrier operations |
—
|
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: boundary layer control for carrier operations | Statement: [Buccaneer S.1, takeoffAndLandingAid, boundary layer control for carrier operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takeoffAndLandingAid Context triple: [Buccaneer S.1, takeoffAndLandingAid, boundary layer control for carrier operations]
-
A.
aircraftFacility
Indicates that a facility is designed, equipped, or used to support the operation, maintenance, or accommodation of aircraft.
-
B.
regionOfTakeoff
Indicates the geographic region or area from which a takeoff event occurs.
-
C.
runwayLanding
Indicates that an aircraft performs a landing operation on a specific runway.
-
D.
hasLandingFacilities
Indicates that a location or structure is equipped with facilities that allow aircraft or other vehicles to land there.
-
E.
partOfLandingSector
Indicates that one entity constitutes a component or subdivision within a larger landing sector.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.