Triple
T4035839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 26 frigate |
E83824
|
entity |
| Predicate | missionBay |
P53583
|
FINISHED |
| Object | flexible mission bay amidships |
—
|
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: flexible mission bay amidships | Statement: [Type 26 frigate, missionBay, flexible mission bay amidships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionBay Context triple: [Type 26 frigate, missionBay, flexible mission bay amidships]
-
A.
flagshipProgram
Indicates that a program is the primary, most prominent, or most important offering associated with an entity.
-
B.
provinceCapitalAccess
Indicates that a location has direct access or connection to the capital city of its province.
-
C.
bayOf
Indicates that one location is a bay that forms an inlet or coastal indentation associated with another geographic entity, such as a sea, ocean, or coastline.
-
D.
developmentAcademy
Indicates a relationship where an academy is responsible for or involved in the development, training, or educational advancement of individuals or groups.
-
E.
missionLed
Indicates that an entity served as the leader or commander of a particular mission.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb132f6c8190937acd35a6a5a9e4 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:36 p.m.