Triple
T376822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Temple in Jerusalem |
E8389
|
entity |
| Predicate | centralFunction |
P4751
|
FINISHED |
| Object | central sanctuary of Judaism |
—
|
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: central sanctuary of Judaism | Statement: [Second Temple in Jerusalem, centralFunction, central sanctuary of Judaism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralFunction Context triple: [Second Temple in Jerusalem, centralFunction, central sanctuary of Judaism]
-
A.
centralIn
chosen
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
C.
mainCentralPower
Indicates that an entity functions as the primary central authority or dominant power within a given system or context.
-
D.
centralText
Indicates that one text element is positioned or designated as the central or primary text relative to surrounding content or layout.
-
E.
centralQuestion
Indicates that something is the main issue, problem, or inquiry around which a discussion, work, or investigation is focused.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec169a848190a577aa093c878839 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96351cc8190a55adf95f8c27e9e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.