Triple
T33650778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Services division |
E862091
|
entity |
| Predicate | typeOfServiceProvider |
P86906
|
FINISHED |
| Object | maritime service provider |
—
|
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: maritime service provider | Statement: [Marine Services division, typeOfServiceProvider, maritime service provider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfServiceProvider Context triple: [Marine Services division, typeOfServiceProvider, maritime service provider]
-
A.
serviceProviderType
chosen
Indicates the category or kind of service provider associated with an entity or transaction.
-
B.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
C.
servicePatternType
Indicates the type or category of service pattern that characterizes how a service is structured, scheduled, or delivered.
-
D.
providerOf
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
E.
hasServiceProvider
Indicates that an entity is associated with or supported by a specific service provider.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00c07b302081908bf9755f8fdbc36e |
completed | May 10, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_6a00bfffb168819084b65804d601896d |
completed | May 10, 2026, 5:27 p.m. |
Created at: May 1, 2026, 1:42 a.m.