Triple
T27529910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Nevada |
E694942
|
entity |
| Predicate | arrivalRelatedTo |
P162679
|
FINISHED |
| Object | opening of Ellis Island immigration station |
—
|
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 Ellis Island immigration station | Statement: [SS Nevada, arrivalRelatedTo, opening of Ellis Island immigration station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivalRelatedTo Context triple: [SS Nevada, arrivalRelatedTo, opening of Ellis Island immigration station]
-
A.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
B.
arrivalFrom
Indicates that an entity arrives at a location or state originating from a specified source location or state.
-
C.
arrivalEventKnownAs
Indicates that a particular arrival event is referred to or identified by a specific name or label.
-
D.
arrivalByShip
Indicates that an entity reaches a destination specifically by traveling on a ship.
-
E.
arrivalTimePattern
Indicates a recurring or structured pattern in the times at which an entity arrives.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f32f4c48190a1cf9004510caab3 |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 1:25 p.m.