Triple
T4816448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loyola College |
E107599
|
entity |
| Predicate | affiliationBeforeMerger |
P59817
|
FINISHED |
| Object | Jesuit educational network |
—
|
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 educational network | Statement: [Loyola College, affiliationBeforeMerger, Jesuit educational network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliationBeforeMerger Context triple: [Loyola College, affiliationBeforeMerger, Jesuit educational network]
-
A.
governingBodyAtMerger
Indicates the organization or authority that served as the governing body of an entity at the time it merged with another entity.
-
B.
formerOrganization
Indicates that an entity was previously affiliated with or employed by a given organization, but is no longer associated with it.
-
C.
foundedByMergerOf
Indicates that an entity was created through the merger or combination of two or more predecessor entities.
-
D.
parentCompanyAfterMerger
Indicates that one company is the resulting parent company of another following a merger.
-
E.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6dda5e808190a26ec85e4499d8e4 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:23 p.m.