Triple
T2024421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberal Judaism (UK) |
E44174
|
entity |
| Predicate | welcomes |
P18449
|
FINISHED |
| Object | interfaith families |
—
|
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: interfaith families | Statement: [Liberal Judaism (UK), welcomes, interfaith families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: welcomes Context triple: [Liberal Judaism (UK), welcomes, interfaith families]
-
A.
welcomesNewMembers
Indicates that an entity actively receives and accepts new members into its group, organization, or community.
-
B.
welcomesParticipantsOf
chosen
Indicates that one entity receives or greets the participants associated with another entity in a friendly or accepting manner.
-
C.
reception
Indicates the act of receiving or welcoming someone or something, often marking the initial acknowledgment or acceptance in an interaction or process.
-
D.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
E.
boarding
Indicates that one entity is getting onto or entering a vehicle, vessel, or similar conveyance associated with another 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f2cd5c8190b19da6f6aa2001d6 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.