Triple
T21943803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsimtsum |
E541885
|
entity |
| Predicate | diegeticTimeOfSinking |
P18834
|
FINISHED |
| Object | During voyage from India to North America |
—
|
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: During voyage from India to North America | Statement: [Tsimtsum, diegeticTimeOfSinking, During voyage from India to North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diegeticTimeOfSinking Context triple: [Tsimtsum, diegeticTimeOfSinking, During voyage from India to North America]
-
A.
missionAtTimeOfSinking
Indicates that a vessel was engaged in a specific mission or operational role at the time it sank.
-
B.
sinkingConsequence
Indicates the outcome or effect that results from something sinking.
-
C.
sunkDuring
chosen
Indicates that one entity was sunk in the course of, or as a result of, the event or time period represented by another entity.
-
D.
sinkingRecordedOnFilm
Indicates that the act or process of sinking was captured or documented on film.
-
E.
sunkInBodyOfWater
Indicates that an object or entity has gone beneath the surface and come to rest within a body of water.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1242515ec8190b015bf8c7b13be85 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:56 p.m.