Triple
T113670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Am Yisrael |
E2297
|
entity |
| Predicate | hasTemporalScope |
P302
|
FINISHED |
| Object | biblical period to present |
—
|
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: biblical period to present | Statement: [Am Yisrael, hasTemporalScope, biblical period to present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalScope Context triple: [Am Yisrael, hasTemporalScope, biblical period to present]
-
A.
temporalRelation
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
-
B.
hasSpacetimeRegion
Indicates that something occupies, is associated with, or is bounded by a specific region in spacetime.
-
C.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
E.
hasLongTermDatasetSince
Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in time.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564417848190a8a8a38e97348963 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.