Triple
T2291967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Medical Center |
E51523
|
entity |
| Predicate | foundedAsCurrentEntity |
P18933
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Boston Medical Center, foundedAsCurrentEntity, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCurrentEntity Context triple: [Boston Medical Center, foundedAsCurrentEntity, 1996]
-
A.
isFormerEntity
Indicates that an entity previously held a particular status, role, or identity but no longer does so.
-
B.
foundedAsCurrentConfiguration
chosen
Indicates that an entity was originally established in the same organizational or structural form in which it currently exists.
-
C.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
D.
foundedAsPartOf
Indicates that an entity was established as a component, division, or subset of a larger existing organization, project, or structure.
-
E.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:48 p.m.