Triple
T32021064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 21 frigate |
E817689
|
entity |
| Predicate | postRoyalNavyOperator |
P173496
|
FINISHED |
| Object | Pakistan Navy |
—
|
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: Pakistan Navy | Statement: [Type 21 frigate, postRoyalNavyOperator, Pakistan Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postRoyalNavyOperator Context triple: [Type 21 frigate, postRoyalNavyOperator, Pakistan Navy]
-
A.
RoyalNavyDesignation
Indicates that an entity has been assigned an official designation or identifier by the Royal Navy.
-
B.
statusWithRoyalNavy
Indicates the formal standing, role, or condition an entity has in relation to the Royal Navy (e.g., active service, retired, affiliated, or none).
-
C.
navalClassNameInRoyalNavy
Indicates that a given naval class name is the designation used for that class within the Royal Navy.
-
D.
navalOperationsBy
Indicates that a set of naval operations is conducted, controlled, or carried out by a specified agent or organization.
-
E.
navalFacilityOperator
Indicates that one entity is responsible for operating, managing, or running a naval facility associated with another entity.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:16 a.m.