Triple
T29097755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knickerbocker Hospital |
E735055
|
entity |
| Predicate | depictedAsServing |
P33500
|
FINISHED |
| Object | immigrant communities |
—
|
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: immigrant communities | Statement: [Knickerbocker Hospital, depictedAsServing, immigrant communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictedAsServing Context triple: [Knickerbocker Hospital, depictedAsServing, immigrant communities]
-
A.
intendedToServe
chosen
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
B.
typicallyServedAs
Indicates that something is most commonly presented, used, or offered in a particular role, form, or function.
-
C.
servesPartOf
Indicates that one entity functions as a service or provider that operates within, or as a component of, another larger system or context.
-
D.
crewServed
Indicates that the operation or use of something requires a coordinated effort by multiple people acting together as a crew.
-
E.
marketedAsServing
Indicates that something is promoted or advertised as providing service to a particular audience, purpose, or function.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 11:10 a.m.