Triple
T18647544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambassadors |
E455840
|
entity |
| Predicate | homeInstitutionFounded |
P26855
|
FINISHED |
| Object | 1896 |
—
|
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: 1896 | Statement: [Ambassadors, homeInstitutionFounded, 1896]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeInstitutionFounded Context triple: [Ambassadors, homeInstitutionFounded, 1896]
-
A.
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.
-
B.
foundedAtInstitution
Indicates that an entity (such as an organization, company, or group) was established or created at a particular institution.
-
C.
foundedWithInstitution
Indicates that an entity was established or created in conjunction with, or through the involvement of, a particular institution.
-
D.
associatedInstitutionFounded
Indicates that the referenced institution was founded or established by, or in direct connection with, the subject entity.
-
E.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500f007c81908b1835569be913d7 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.