Triple
T9085604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dejima |
E217744
|
entity |
| Predicate | functionEndedWith |
P56380
|
FINISHED |
| Object | opening of Japan in the 1850s |
—
|
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: opening of Japan in the 1850s | Statement: [Dejima, functionEndedWith, opening of Japan in the 1850s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionEndedWith Context triple: [Dejima, functionEndedWith, opening of Japan in the 1850s]
-
A.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
B.
functionEnd
chosen
Indicates the point or condition at which a function, process, or operation terminates or completes.
-
C.
useEnded
Indicates that an entity’s period of using or employing another entity has come to an end.
-
D.
endsWith
Indicates that one entity terminates with, or has as its final part, the sequence or element represented by the other entity.
-
E.
blendsWith
Indicates that one entity can be mixed or combined smoothly with another to form a uniform or harmonious result.
- 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_69ca83d7a0388190ba1af89ed7ba36f9 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc960d0b008190b0e9e61fac45101d |
completed | April 1, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:13 p.m.