Triple
T317175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellis Island |
E7732
|
entity |
| Predicate | servedAsPrimaryEntryPointFor |
P2958
|
FINISHED |
| Object | immigrants to the United States |
—
|
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: immigrants to the United States | Statement: [Ellis Island, servedAsPrimaryEntryPointFor, immigrants to the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsPrimaryEntryPointFor Context triple: [Ellis Island, servedAsPrimaryEntryPointFor, immigrants to the United States]
-
A.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
B.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
C.
primaryHubFor
chosen
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
D.
primaryInterface
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
-
E.
servedAs
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea65ca7081908093e6aaaf2d34f7 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e943f12c8190883854aeed974260 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.