Triple
T19082840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outer Court |
E467071
|
entity |
| Predicate | separationFunction |
P105874
|
FINISHED |
| Object | boundary between sacred space and camp of Israel |
—
|
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: boundary between sacred space and camp of Israel | Statement: [Outer Court, separationFunction, boundary between sacred space and camp of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separationFunction Context triple: [Outer Court, separationFunction, boundary between sacred space and camp of Israel]
-
A.
separatedFunctionFrom
Indicates that one entity has been detached or removed from performing a particular function or role in relation to another entity.
-
B.
separationMethod
Indicates the technique or process used to separate one substance, component, or entity from another.
-
C.
typeOfSeparation
Indicates the specific manner or category of separation that exists or occurred between entities.
-
D.
separationProcess
Indicates a process in which components of a mixture or system are divided or isolated from one another based on differing properties or conditions.
-
E.
definedSeparationFrom
chosen
Indicates a formally specified distinction or boundary established between one entity and another.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2eab58c8190a987c88d633c92ec |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.