Triple
T32581016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essex-class aircraft carrier |
E832784
|
entity |
| Predicate | firstShipLaidDown |
P34263
|
FINISHED |
| Object | USS Essex (CV-9) |
E87304
|
NE 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: USS Essex (CV-9) | Statement: [Essex-class aircraft carrier, firstShipLaidDown, USS Essex (CV-9)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstShipLaidDown Context triple: [Essex-class aircraft carrier, firstShipLaidDown, USS Essex (CV-9)]
-
A.
dateOfKeelLaying
Indicates the calendar date on which the keel of a vessel was formally laid, marking the official start of its construction.
-
B.
thirdShipLaunched
Indicates that an entity is the third ship to be launched in a particular sequence or context.
-
C.
firstShip
chosen
Indicates that the subject is the earliest or initial ship associated with, created by, or used in relation to the object.
-
D.
hullConstructedIn
Indicates that the hull of an object (such as a ship or vessel) was built or constructed at a specific location or facility.
-
E.
originalShipLaunchedIn
Indicates that an original ship was first launched in a specified year, place, or context.
- F. None of above.
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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347ba4b6688190b00be334e6f75b0c |
completed | June 18, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:04 a.m.