Triple
T20758562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Lionfish (SS-298) |
E510910
|
entity |
| Predicate | museumRole |
P69200
|
FINISHED |
| Object | exhibit on submarine warfare |
—
|
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: exhibit on submarine warfare | Statement: [USS Lionfish (SS-298), museumRole, exhibit on submarine warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: museumRole Context triple: [USS Lionfish (SS-298), museumRole, exhibit on submarine warfare]
-
A.
operatesMuseum
Indicates that one entity manages and runs the day-to-day operations of a museum.
-
B.
associatedWithMuseum
Indicates a relationship where an entity has a formal or recognized connection to a museum, such as ownership, curation, exhibition, or institutional affiliation.
-
C.
exhibitionRole
chosen
Indicates the specific function or capacity an entity has within the context of an exhibition (e.g., organizer, curator, exhibitor, or participant).
-
D.
museumHolds
Indicates that a museum possesses, preserves, or has custody of a particular item or collection within its holdings.
-
E.
hasMuseumFunction
Indicates that an entity serves the role or performs the function of a museum.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2464fb08190b6b141ca12d9f3f4 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:35 p.m.