Triple
T31518676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Chatelain (DE-149) |
E804144
|
entity |
| Predicate | hasSpeedType |
P140422
|
FINISHED |
| Object | typical destroyer escort speed |
—
|
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: typical destroyer escort speed | Statement: [USS Chatelain (DE-149), hasSpeedType, typical destroyer escort speed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeedType Context triple: [USS Chatelain (DE-149), hasSpeedType, typical destroyer escort speed]
-
A.
hasSpeedRegime
chosen
Indicates a relationship where an entity is associated with a particular speed range or operating speed condition under which it functions or is evaluated.
-
B.
hasTopSpeedSection
Indicates that an entity includes or is associated with a segment or portion where the maximum or top speed is defined, reached, or relevant.
-
C.
speedSupervisionType
Indicates the type or mode of speed control or monitoring applied to an entity (e.g., how its speed is regulated or supervised).
-
D.
hasServiceSpeed
Indicates that an entity provides a service operating at a specified speed or performance rate.
-
E.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 30, 2026, 9:54 p.m.