Triple
T2251763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimitz-class aircraft carrier |
E49631
|
entity |
| Predicate | hasFlightDeckType |
P23967
|
FINISHED |
| Object | angled flight deck |
—
|
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: angled flight deck | Statement: [Nimitz-class aircraft carrier, hasFlightDeckType, angled flight deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightDeckType Context triple: [Nimitz-class aircraft carrier, hasFlightDeckType, angled flight deck]
-
A.
flightDeckType
chosen
Indicates the specific configuration or design type of a vehicle’s flight deck (cockpit/control area).
-
B.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another entity.
-
C.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
D.
hasBasedAircraft
Indicates that an aircraft is regularly stationed or primarily based at a particular location or facility.
-
E.
hasAircraftOnDisplay
Indicates that an entity exhibits or presents an aircraft as part of a display or collection.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11d04688190abc04fac3a1804a9 |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.