Triple
T30377764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Cyane |
E772737
|
entity |
| Predicate | previousServiceBranch |
P195541
|
FINISHED |
| Object | Royal 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: Royal Navy | Statement: [USS Cyane, previousServiceBranch, Royal Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousServiceBranch Context triple: [USS Cyane, previousServiceBranch, Royal Navy]
-
A.
previousBranch
Indicates that one branch directly precedes another in an ordered sequence of branches.
-
B.
originalServiceBranch
Indicates the military or organizational service branch in which an individual initially served or was first enlisted.
-
C.
previousServiceType
Indicates that one service type directly preceded another in a sequence or history of services.
-
D.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
-
E.
previousRepository
Indicates that one repository directly precedes another in a version, history, or sequence of repositories.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69fdd922d73c81908ad3faade247ec16 |
completed | May 8, 2026, 12:37 p.m. |
Created at: April 29, 2026, 8 p.m.