Triple
T28731954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbiad |
E730682
|
entity |
| Predicate | hasFiringPurpose |
P184323
|
FINISHED |
| Object | countering enemy warships |
—
|
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: countering enemy warships | Statement: [Columbiad, hasFiringPurpose, countering enemy warships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFiringPurpose Context triple: [Columbiad, hasFiringPurpose, countering enemy warships]
-
A.
firingPurpose
chosen
Indicates the reason or intended objective behind initiating a firing or discharge action.
-
B.
canBeFiredIn
Indicates that an entity (such as a weapon or device) is capable of being discharged or operated within a specified medium, environment, or container.
-
C.
designedToFire
Indicates that one entity is intended or configured to discharge, launch, or emit another entity (such as a projectile, signal, or event).
-
D.
hasEstablishedPurpose
Indicates that an entity has a defined and recognized purpose or intended function already determined.
-
E.
hasFiringRange
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 28, 2026, 5:58 a.m.