Triple
T1134398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenox Library, New York City |
E23104
|
entity |
| Predicate | establishedAsInstitution |
P1833
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Lenox Library, New York City, establishedAsInstitution, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsInstitution Context triple: [Lenox Library, New York City, establishedAsInstitution, 19th century]
-
A.
establishedInstitution
chosen
Indicates that an entity founded, created, or formally set up an institution or organization.
-
B.
recognizedAsInstitutionBy
Indicates that an entity is acknowledged or accepted as an institution by a specified recognizing party.
-
C.
servesInstitution
Indicates that one entity provides services or functions in support of a particular institution.
-
D.
grantedByInstitution
Indicates that something (such as a status, permission, or resource) is conferred or authorized by an institution.
-
E.
associatedWithInstitution
Indicates that an entity has a formal or recognized connection or affiliation with an institution.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.