Triple
T3910315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Essex (CV-9) |
E87304
|
entity |
| Predicate | flightDeckBeam |
P37490
|
FINISHED |
| Object | about 147 feet |
—
|
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: about 147 feet | Statement: [USS Essex (CV-9), flightDeckBeam, about 147 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightDeckBeam Context triple: [USS Essex (CV-9), flightDeckBeam, about 147 feet]
-
A.
flightDeckType
Indicates the specific configuration or design type of a vehicle’s flight deck (cockpit/control area).
-
B.
flightDeckWidth
chosen
Indicates the measurement of how wide a vehicle’s flight deck is across its lateral (side-to-side) dimension.
-
C.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another entity.
-
D.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
-
E.
hardpoints
Indicates a relationship where one entity provides designated attachment locations or mounting interfaces on its structure for connecting other components or equipment.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.