Triple
T17893505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbaros Hayreddin (battleship) |
E447376
|
entity |
| Predicate | serviceEntryInOttomanNavy |
P129205
|
FINISHED |
| Object | 1910s |
—
|
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: 1910s | Statement: [Barbaros Hayreddin (battleship), serviceEntryInOttomanNavy, 1910s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEntryInOttomanNavy Context triple: [Barbaros Hayreddin (battleship), serviceEntryInOttomanNavy, 1910s]
-
A.
shipsAndPersonnel
Indicates a relationship involving both ships and their associated personnel, such as assignment, deployment, or operational linkage between them.
-
B.
navalOperationsBy
Indicates that a set of naval operations is conducted, controlled, or carried out by a specified agent or organization.
-
C.
allowedSeaService
Indicates that an entity is permitted or authorized to perform or accrue service at sea.
-
D.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
E.
servedHarbour
Indicates that an entity provided service, support, or functions related to a harbour or port.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7b57bc8190995e40134215cdfd |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:19 a.m.