Triple
T34379296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (2011) |
E882383
|
entity |
| Predicate | hasServiceDomain |
P201041
|
FINISHED |
| Object | international waters |
—
|
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: international waters | Statement: [SS Empress of Britain (2011), hasServiceDomain, international waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceDomain Context triple: [SS Empress of Britain (2011), hasServiceDomain, international waters]
-
A.
hasDomainFeature
Indicates that something possesses or is characterized by a specific feature or attribute within a particular domain or context.
-
B.
hasPossibleDomain
Indicates that a property or relation may apply to, or be defined over, a particular class or type of entities, without asserting that this is its only or actual domain.
-
C.
hasServiceFrom
Indicates that one entity receives or benefits from a service provided by another entity.
-
D.
hasDomainZone
Indicates that one entity possesses, controls, or is associated with a specific domain zone within a larger domain or namespace.
-
E.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
| PDg | Predicate description generation | batch_69ffc3eed97c819085c06ffe3699ff38 |
completed | May 9, 2026, 11:31 p.m. |
Created at: May 1, 2026, 1:59 a.m.