Triple
T3359852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Shuwaikh |
E70693
|
entity |
| Predicate | hasPilotageServices |
P25928
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Port of Shuwaikh, hasPilotageServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilotageServices Context triple: [Port of Shuwaikh, hasPilotageServices, yes]
-
A.
hasPilotage
chosen
Indicates a relationship where one entity provides or is subject to navigational guidance or piloting services by another entity.
-
B.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
C.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
D.
hasPilotis
Indicates that a building or structure is elevated on pilotis (supporting columns or stilts), rather than resting directly on the ground.
-
E.
hasGroundHandlingServices
Indicates that an entity provides or is associated with ground handling services for another entity, typically in an aviation or transportation context.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb266c4a881908aded39ccb8f43b2 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.