Triple
T34488473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FRAM I modernization program |
E885397
|
entity |
| Predicate | targetShipType |
P6545
|
FINISHED |
| Object | 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: destroyer | Statement: [FRAM I modernization program, targetShipType, destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetShipType Context triple: [FRAM I modernization program, targetShipType, destroyer]
-
A.
targetedShip
Indicates that one entity has selected or designated a particular ship as the focus of its attention or action, such as for attack, tracking, or interaction.
-
B.
originalShipType
chosen
Indicates the type or category of ship that an entity was originally classified or built as.
-
C.
typicalShipTypes
Indicates that the subject is commonly or characteristically associated with the specified types or categories of ships.
-
D.
laterShipType
Indicates that one ship type chronologically succeeds or is introduced after another ship type.
-
E.
shipClass
Indicates the classification or type category to which a particular ship belongs.
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 1, 2026, 2:01 a.m.