Triple
T34384166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Msida Marina |
E882513
|
entity |
| Predicate | hasApproximateBerthCapacity |
P82090
|
FINISHED |
| Object | over 700 berths |
—
|
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: over 700 berths | Statement: [Msida Marina, hasApproximateBerthCapacity, over 700 berths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateBerthCapacity Context triple: [Msida Marina, hasApproximateBerthCapacity, over 700 berths]
-
A.
numberOfBerths
chosen
Indicates the quantity of berths (sleeping places or docking spaces) associated with an entity.
-
B.
hasBerths
Indicates that one entity provides or contains sleeping or docking berths for another entity.
-
C.
hasBerthLength
Indicates the length of a berth allocated to or associated with an entity.
-
D.
hasBerthDepth
Indicates the depth of water available at a specific berth where a vessel can be moored.
-
E.
missionBayCapacity
Indicates the capacity or maximum volume that Mission Bay can hold or accommodate.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 1, 2026, 1:59 a.m.