Triple
T35540379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Carpathia |
E1027042
|
entity |
| Predicate | arrivedAtTitanicSite |
P183397
|
FINISHED |
| Object | about 4 am, 1912-04-15 |
—
|
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: about 4 am, 1912-04-15 | Statement: [RMS Carpathia, arrivedAtTitanicSite, about 4 am, 1912-04-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivedAtTitanicSite Context triple: [RMS Carpathia, arrivedAtTitanicSite, about 4 am, 1912-04-15]
-
A.
departedTitanicSite
Indicates that an entity has left or moved away from the location associated with the Titanic site.
-
B.
startTimeOnTitanic
Indicates the time at which an event or activity begins on the Titanic.
-
C.
routeAtTimeOfSinking
Indicates the specific route an entity (such as a vessel) was following at the time it sank.
-
D.
Waterline
Indicates the level or line on an object or surface that marks where water reaches or has reached.
-
E.
madeLandfallAt
Indicates that a storm or similar weather system has come ashore at a specific geographic 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.