Triple
T3886412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portsmouth Naval Base |
E92950
|
entity |
| Predicate | hasBerthFor |
P27883
|
FINISHED |
| Object | aircraft carriers |
—
|
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: aircraft carriers | Statement: [Portsmouth Naval Base, hasBerthFor, aircraft carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBerthFor Context triple: [Portsmouth Naval Base, hasBerthFor, aircraft carriers]
-
A.
hasBerths
chosen
Indicates that one entity provides or contains sleeping or docking berths for another entity.
-
B.
determinedBerthIn
Indicates that an entity has been assigned or allocated to a specific berth or docking position.
-
C.
berthType
Indicates the specific kind or category of berth associated with an entity, such as the type of sleeping or docking space provided.
-
D.
berthingOrDockingTarget
Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
-
E.
hasBerthDepth
Indicates the depth of water available at a specific berth where a vessel can be moored.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec942bfc8190a398fe370715a28b |
completed | March 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.