Triple
T13682464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boneh Yerushalayim |
E328034
|
entity |
| Predicate | coreRequest |
P111151
|
FINISHED |
| Object | God’s compassion on Israel, His people |
—
|
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: God’s compassion on Israel, His people | Statement: [Boneh Yerushalayim, coreRequest, God’s compassion on Israel, His people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreRequest Context triple: [Boneh Yerushalayim, coreRequest, God’s compassion on Israel, His people]
-
A.
centralRequest
Indicates that an entity serves as the primary or main request within a broader set of related requests or interactions.
-
B.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
-
C.
requiresResponse
Indicates that an action, event, or communication necessitates a reply or follow-up response from another party.
-
D.
core
Indicates a central, most important, or foundational part of something in relation to its surrounding or supporting elements.
-
E.
requestContent
Indicates that one entity asks another entity to provide specific information, data, or material.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.