Triple
T26457847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formidable-class frigate |
E665541
|
entity |
| Predicate | allShipsNamed |
P160768
|
FINISHED |
| Object | RSS Formidable |
—
|
NE NERFINISHED |
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: RSS Formidable | Statement: [Formidable-class frigate, allShipsNamed, RSS Formidable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allShipsNamed Context triple: [Formidable-class frigate, allShipsNamed, RSS Formidable]
-
A.
shipName
Indicates the name assigned to a specific ship in the relationship.
-
B.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
C.
numberOfShips
Indicates the quantity of ships associated with a given entity or situation.
-
D.
fleetName
Indicates the name assigned to a particular fleet within a system or context.
-
E.
shipsOfTheLine
Indicates a relationship where the associated entities are classified as ships of the line, i.e., major warships designed to participate in the main line of battle.
- F. None of above. chosen
Provenance (4 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61291b9588190931535163a538686 |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 27, 2026, 12:10 a.m.