Triple
T21434451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mathematical-Physical Salon |
E528770
|
entity |
| Predicate | foundedAsCollection |
P364
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Mathematical-Physical Salon, foundedAsCollection, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCollection Context triple: [Mathematical-Physical Salon, foundedAsCollection, 16th century]
-
A.
formerCollectionOf
Indicates that an entity once served as a collection or repository for another entity, but no longer holds that role.
-
B.
foundedAs
chosen
Indicates the original name or form under which an organization, institution, or entity was first established.
-
C.
foundedAsOneOf
Indicates that an entity was originally established as one member of a group or set of entities founded together.
-
D.
foundedAsGrouping
Indicates that an entity was originally established or created as part of a particular group, category, or organizational grouping.
-
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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b53516d081908f8058a8ee363629 |
completed | April 22, 2026, 11:47 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 6 p.m.