Triple
T37131470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Jersey |
E919527
|
entity |
| Predicate | crewLoyalty |
P161348
|
FINISHED |
| Object | Loyalist guards and British personnel |
—
|
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: Loyalist guards and British personnel | Statement: [HMS Jersey, crewLoyalty, Loyalist guards and British personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewLoyalty Context triple: [HMS Jersey, crewLoyalty, Loyalist guards and British personnel]
-
A.
loyalCrewMembers
chosen
Indicates that certain crew members consistently support, obey, and remain faithful to a leader, group, or mission.
-
B.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
-
C.
crewHonored
Indicates that a crew has been formally recognized or celebrated for their actions, service, or achievements.
-
D.
teamLoyalty
Indicates a relationship where an individual consistently supports, commits to, and prioritizes the interests of a particular team over alternatives.
-
E.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.