Triple
T13682447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boneh Yerushalayim |
E328034
|
entity |
| Predicate | containsPetitionFor |
P14344
|
FINISHED |
| Object | rebuilding of Jerusalem |
—
|
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: rebuilding of Jerusalem | Statement: [Boneh Yerushalayim, containsPetitionFor, rebuilding of Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPetitionFor Context triple: [Boneh Yerushalayim, containsPetitionFor, rebuilding of Jerusalem]
-
A.
containsPetition
chosen
Indicates that one entity includes or holds a petition within it, either as content or as a component.
-
B.
canBePetitionedBy
Indicates that an entity is eligible to receive formal petitions, requests, or appeals from another entity.
-
C.
numberOfPetitions
Indicates the total count of petitions associated with a given entity or context.
-
D.
partyTypePetitioners
Indicates that the associated parties in a legal case are classified as petitioners.
-
E.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
- 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_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. |
Created at: April 9, 2026, 9:53 p.m.