Triple
T33170705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shimoda |
E849021
|
entity |
| Predicate | BlackShipFestivalCommemorates |
P176151
|
FINISHED |
| Object | arrival of Commodore Perry’s Black Ships |
—
|
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: arrival of Commodore Perry’s Black Ships | Statement: [Shimoda, BlackShipFestivalCommemorates, arrival of Commodore Perry’s Black Ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BlackShipFestivalCommemorates Context triple: [Shimoda, BlackShipFestivalCommemorates, arrival of Commodore Perry’s Black Ships]
-
A.
shipFlag
Indicates that a ship is registered under and legally operates under the authority of a specified national flag or registry.
-
B.
shipCompanion
Indicates that one entity serves as a companion or partner accompanying another entity on a ship or sea voyage.
-
C.
shipFeatured
Indicates that a particular ship is highlighted or promoted as a featured item in a given context.
-
D.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
E.
shipsTo
Indicates that one entity sends or delivers goods, products, or items to another entity or location.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:28 a.m.