Triple
T28733362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collegium Gostomianum |
E730724
|
entity |
| Predicate | hasFoundingIntention |
P145011
|
FINISHED |
| Object | Jesuit education in Sandomierz |
—
|
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: Jesuit education in Sandomierz | Statement: [Collegium Gostomianum, hasFoundingIntention, Jesuit education in Sandomierz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoundingIntention Context triple: [Collegium Gostomianum, hasFoundingIntention, Jesuit education in Sandomierz]
-
A.
goalAtFounding
chosen
Indicates that an entity had a particular goal or intended purpose at the time it was founded.
-
B.
aimedToEstablish
Indicates an intention or effort directed toward creating, founding, or setting up something.
-
C.
hasFoundation
Indicates that an entity is supported, established, or based upon a particular foundation or underlying basis.
-
D.
hasEstablishedPurpose
Indicates that an entity has a defined and recognized purpose or intended function already determined.
-
E.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 28, 2026, 5:59 a.m.