Triple
T38703446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lütjens-class destroyer |
E950199
|
entity |
| Predicate | enteredServiceWithGermanNavy |
P178340
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [Lütjens-class destroyer, enteredServiceWithGermanNavy, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredServiceWithGermanNavy Context triple: [Lütjens-class destroyer, enteredServiceWithGermanNavy, 1969]
-
A.
enteredBritishService
Indicates that an entity began serving in an official capacity under British authority or institutions.
-
B.
enteredServiceWithRoyalCanadianNavy
Indicates that an entity began active duty or operational service under the authority of the Royal Canadian Navy.
-
C.
enteredServiceInNavy
chosen
Indicates that an entity began active duty or formal service in a navy on a specified date or during a specified time period.
-
D.
enteredHarbour
Indicates that an entity has moved into and arrived within the boundaries of a harbour.
-
E.
GneisenauOperator
Indicates that an entity serves as the operator or controlling organization responsible for Gneisenau.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:33 p.m.