Triple
T27995323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AK-630 |
E706995
|
entity |
| Predicate | typicalMountingPlatform |
P38304
|
FINISHED |
| Object | surface combatant ship |
—
|
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: surface combatant ship | Statement: [AK-630, typicalMountingPlatform, surface combatant ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMountingPlatform Context triple: [AK-630, typicalMountingPlatform, surface combatant ship]
-
A.
typicalPlatform
chosen
Indicates that something commonly or usually serves as the platform or environment on which another thing operates, appears, or is based.
-
B.
canBePlacedOn
Indicates that one entity is allowed or able to be positioned or set on top of another entity.
-
C.
onboardPlatform
Indicates that an entity is being added, integrated, or enrolled onto a particular platform so it can start operating or participating there.
-
D.
partOfPlatform
Indicates that one entity functions as a component or constituent element within a larger platform.
-
E.
hasPlatformOn
Indicates that one entity is physically supported by or situated on the surface or structure of another entity.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a004fd3caf48190b2ec063a7bf0756b |
completed | May 10, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a004f7672dc8190aca91d1ed855bf9a |
completed | May 10, 2026, 9:27 a.m. |
Created at: April 27, 2026, 7:53 p.m.