Triple
T27955678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (CVN-80) |
E703540
|
entity |
| Predicate | shipNamingAuthority |
P163805
|
FINISHED |
| Object | United States Secretary of the Navy |
—
|
NE NERFINISHED |
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: United States Secretary of the Navy | Statement: [USS Enterprise (CVN-80), shipNamingAuthority, United States Secretary of the Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipNamingAuthority Context triple: [USS Enterprise (CVN-80), shipNamingAuthority, United States Secretary of the Navy]
-
A.
shipRegistry
Indicates that an entity is officially recorded or listed in a particular ship registry or registration system.
-
B.
navalName
Indicates that an entity has a specific name used in a naval or maritime context.
-
C.
countryNamingAuthority
Indicates that an entity serves as the official authority responsible for assigning or approving the names of countries.
-
D.
shipName
Indicates the name assigned to a specific ship in the relationship.
-
E.
fleetName
Indicates the name assigned to a particular fleet within a system or context.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 7:27 p.m.