Triple
T36878712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Cardiff (Type 26 frigate) |
E911413
|
entity |
| Predicate | programmeRole |
P186636
|
FINISHED |
| Object | second Type 26 frigate for the Royal Navy |
—
|
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: second Type 26 frigate for the Royal Navy | Statement: [HMS Cardiff (Type 26 frigate), programmeRole, second Type 26 frigate for the Royal Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmeRole Context triple: [HMS Cardiff (Type 26 frigate), programmeRole, second Type 26 frigate for the Royal Navy]
-
A.
profileRole
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
-
B.
roleOfPerson
Indicates that a specific role, function, or position is assigned to or held by a particular person.
-
C.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
D.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
E.
codeRole
Indicates a relationship where an entity serves a specific role or function within a piece of code or software system.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.