Triple
T32276179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Katahdin |
E824550
|
entity |
| Predicate | designAssessment |
P126837
|
FINISHED |
| Object | considered unsuccessful as a warship concept |
—
|
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: considered unsuccessful as a warship concept | Statement: [USS Katahdin, designAssessment, considered unsuccessful as a warship concept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designAssessment Context triple: [USS Katahdin, designAssessment, considered unsuccessful as a warship concept]
-
A.
designAspect
Indicates that one entity represents a particular design-related feature, characteristic, or consideration of another entity.
-
B.
designCheck
Indicates that an entity performs a review or verification of a design to ensure it meets specified requirements or standards.
-
C.
designOutcome
chosen
Indicates the result, effect, or consequence produced by a particular design or design process.
-
D.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
E.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: May 1, 2026, 12:43 a.m.