Triple
T4596480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puckman |
E100215
|
entity |
| Predicate | representsInstitutionFoundedIn |
P26855
|
FINISHED |
| Object | 1824 |
—
|
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: 1824 | Statement: [Puckman, representsInstitutionFoundedIn, 1824]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsInstitutionFoundedIn Context triple: [Puckman, representsInstitutionFoundedIn, 1824]
-
A.
foundedWithInstitution
Indicates that an entity was established or created in conjunction with, or through the involvement of, a particular institution.
-
B.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
-
C.
homeInstitutionFoundedIn
chosen
Indicates that the institution serving as a home or primary affiliation for an entity was established in a specified year or time period.
-
D.
awardingBodyFoundedIn
Indicates the year or date when the awarding body (the organization that grants awards) was established or founded.
-
E.
foundingLocationOfFoundedOrganization
Indicates the place where an organization was originally established or founded.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd594055dc8190a50f1b4be2be1ba0 |
completed | March 20, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.