Triple
T27201404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Watson |
E683743
|
entity |
| Predicate | isShoreEstablishment |
P162248
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [HMAS Watson, isShoreEstablishment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShoreEstablishment Context triple: [HMAS Watson, isShoreEstablishment, true]
-
A.
isShoreEstablishmentOf
Indicates that one entity is a land-based (shore) facility that belongs to, supports, or is administratively part of another maritime or naval organization or unit.
-
B.
isCoastalBuilding
Indicates that a building is located on or very near a coastline, typically adjacent to or directly influenced by a sea or ocean.
-
C.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
D.
hasShoreFeature
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
E.
hasShorelineUse
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625e103708190a70b45ee141c37b2 |
completed | May 2, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:36 a.m.