Triple
T4709503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 21 |
E104473
|
entity |
| Predicate | operatedAsImmigrationShedFrom |
P59107
|
FINISHED |
| Object | 1928 |
—
|
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: 1928 | Statement: [Pier 21, operatedAsImmigrationShedFrom, 1928]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsImmigrationShedFrom Context triple: [Pier 21, operatedAsImmigrationShedFrom, 1928]
-
A.
closedAsImmigrationStation
Indicates that an entity ceased operating in its role as an immigration station.
-
B.
numberOfImmigrantsProcessed
Indicates the total count of immigrants that have been processed in a given context or system.
-
C.
immigrationStationPrimaryUse
Indicates that a particular immigration station is primarily used for a specified main function or purpose within immigration processing or control.
-
D.
separateImmigrationSystemFrom
Indicates that one entity establishes or maintains a distinct immigration system that is independent from another entity’s immigration system.
-
E.
barredImmigrationFrom
Indicates that one entity has officially prohibited or restricted immigration originating from another entity.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd680b06e881908de87edf815f3cc0 |
completed | March 20, 2026, 3:30 p.m. |
Created at: March 20, 2026, 1:17 p.m.