Triple
T24926917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Clamagore (SS-343) |
E618882
|
entity |
| Predicate | openToPublicFrom |
P18215
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [USS Clamagore (SS-343), openToPublicFrom, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openToPublicFrom Context triple: [USS Clamagore (SS-343), openToPublicFrom, 1981]
-
A.
openToPublicAs
Indicates that something (such as a place, resource, or event) is made accessible or available for use, entry, or participation by the general public in a specified capacity or role.
-
B.
openedForPublic
Indicates that something has been made accessible or available for use, entry, or participation by the general public.
-
C.
openedToPublicBy
Indicates that an entity was made accessible or available to the general public through the action or decision of another entity.
-
D.
openToPublicSince
chosen
Indicates that an entity has been accessible or available for use by the general public starting from a specified point in time.
-
E.
hasPartOpenToPublic
Indicates that some portion or component of an entity is accessible for use or visitation by the general public.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f423b0ac18819091801893849a2ca6 |
completed | May 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:29 a.m.