Triple
T34524708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Navy aircraft carriers |
E886368
|
entity |
| Predicate | typicalFlightDeckType |
P23967
|
FINISHED |
| Object | ski-jump STOBAR |
—
|
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: ski-jump STOBAR | Statement: [Indian Navy aircraft carriers, typicalFlightDeckType, ski-jump STOBAR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFlightDeckType Context triple: [Indian Navy aircraft carriers, typicalFlightDeckType, ski-jump STOBAR]
-
A.
flightDeckType
chosen
Indicates the specific configuration or design type of a vehicle’s flight deck (cockpit/control area).
-
B.
cockpitType
Indicates the specific configuration or style of cockpit associated with an entity (e.g., vehicle or aircraft).
-
C.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
D.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another entity.
-
E.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.