Triple
T33000262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beit She'arim National Park |
E844345
|
entity |
| Predicate | timeOfUseAsNecropolis |
P69529
|
FINISHED |
| Object | 2nd century CE |
—
|
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: 2nd century CE | Statement: [Beit She'arim National Park, timeOfUseAsNecropolis, 2nd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfUseAsNecropolis Context triple: [Beit She'arim National Park, timeOfUseAsNecropolis, 2nd century CE]
-
A.
timePeriodOfBurials
Indicates the span of time during which the burials associated with an entity took place.
-
B.
periodOfBurial
chosen
Indicates the time period or date range during which the burial of an entity took place.
-
C.
usedAsGraveUntil
Indicates that something continued to function or be designated as a grave up to a specified point in time.
-
D.
usedAsCemeterySince
Indicates that a place has functioned as a cemetery starting from a specified point in time.
-
E.
usedAsBurialGroundUntil
Indicates that a place functioned as a burial ground up to a specified end time or date.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 1:22 a.m.