Triple
T36186598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tractate Berakhot |
E1046862
|
entity |
| Predicate | originallyCompiled |
P155307
|
FINISHED |
| Object | Land of Israel |
E131616
|
NE 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: Land of Israel | Statement: [Tractate Berakhot, originallyCompiled, Land of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyCompiled Context triple: [Tractate Berakhot, originallyCompiled, Land of Israel]
-
A.
originalCompilation
chosen
Indicates that one work is the initial or primary compilation from which another compiled or derived version originates.
-
B.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
C.
laterCompiledAs
Indicates that one work, version, or material was subsequently gathered, edited, or assembled into another compiled work.
-
D.
compiledTo
Indicates that one artifact (such as source code) has been transformed into another, typically lower-level or executable form, through a compilation process.
-
E.
originallyBy
Indicates that one entity is the original creator, author, or source of another entity.
- F. None of above.
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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a393407e50c81908b993240bd023ecf |
completed | June 22, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.