Triple
T4578665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Congregation of the Society of Jesus |
E101800
|
entity |
| Predicate | meetsIrregularly |
P58103
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [General Congregation of the Society of Jesus, meetsIrregularly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsIrregularly Context triple: [General Congregation of the Society of Jesus, meetsIrregularly, true]
-
A.
meetsRegularly
Indicates that two or more entities come together on a recurring or scheduled basis.
-
B.
meets
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
C.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
-
D.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
-
E.
meetsBetween
Indicates that one entity meets or encounters another at some point between two specified reference points or times.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd58e2a1808190be4582d5b3003d6c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:10 p.m.