Triple
T30851882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gridley-class destroyer |
E785802
|
entity |
| Predicate | typicalSpeedClass |
P9902
|
FINISHED |
| Object | high-speed destroyer |
—
|
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: high-speed destroyer | Statement: [Gridley-class destroyer, typicalSpeedClass, high-speed destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpeedClass Context triple: [Gridley-class destroyer, typicalSpeedClass, high-speed destroyer]
-
A.
speedClass
chosen
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
typicalSpeedEnvironment
Indicates that an environment is characterized by a particular speed that is typical or normal for it.
-
C.
speedClassMarking
Indicates how an entity is categorized or labeled according to its speed characteristics or performance class.
-
D.
typicalTopSpeedRange
Indicates the usual range of maximum speeds that an entity is capable of under normal conditions.
-
E.
recordSpeedCategory
Indicates the classification of an entity’s speed into a predefined category (e.g., slow, normal, fast) based on its recorded speed.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:46 p.m.