Triple
T5641846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Society coat of arms |
E124283
|
entity |
| Predicate | associatedInstitutionFounded |
P65366
|
FINISHED |
| Object | 1660 |
—
|
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: 1660 | Statement: [Royal Society coat of arms, associatedInstitutionFounded, 1660]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedInstitutionFounded Context triple: [Royal Society coat of arms, associatedInstitutionFounded, 1660]
-
A.
foundedWithInstitution
Indicates that an entity was established or created in conjunction with, or through the involvement of, a particular institution.
-
B.
associatedInstitution
Indicates that an entity has a formal connection or affiliation with a particular institution.
-
C.
associatedInstitutionType
Indicates the type or category of institution with which an entity is associated.
-
D.
linkedInstitutionFounder
Indicates that an entity is the founder or co-founder of an institution with which another entity is associated or linked.
-
E.
associatedWithInstitution
Indicates that an entity has a formal or recognized connection or affiliation with an institution.
- F. None of above. chosen
Provenance (4 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a6a22881908d16f4df564ed2a2 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0727bc8190b16e9a669c04b4dd |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:41 p.m.