Triple
T113663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Am Yisrael |
E2297
|
entity |
| Predicate | invokedIn |
P6455
|
FINISHED |
| Object | Jewish communal solidarity |
—
|
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: Jewish communal solidarity | Statement: [Am Yisrael, invokedIn, Jewish communal solidarity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invokedIn Context triple: [Am Yisrael, invokedIn, Jewish communal solidarity]
-
A.
executedWith
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
B.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
canBeCalledInto
Indicates that one entity has the authority or ability to summon, request the presence of, or formally convene another entity.
-
D.
callsFor
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
E.
declaredBy
Indicates that something (such as a statement, variable, or entity) is formally introduced, specified, or announced by a particular agent or source.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564417848190a8a8a38e97348963 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2575d8a648190ad8e10d4b04e5e07 |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.