Triple
T25803060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | נגב |
E649887
|
entity |
| Predicate | כולל אתר ארכאולוגי |
P108844
|
FINISHED |
| Object | ממשית |
—
|
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: ממשית | Statement: [נגב, כולל אתר ארכאולוגי, ממשית]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: כולל אתר ארכאולוגי Context triple: [נגב, כולל אתר ארכאולוגי, ממשית]
-
A.
isArchaeologicalSite
Indicates that a location or structure is recognized as an archaeological site, typically due to its historical or cultural remains of past human activity.
-
B.
modernArchaeologicalSite
Indicates that a location functions as an archaeological site characterized by modern-era remains, research, or excavation activities.
-
C.
hasArchaeologicalSiteIn
chosen
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
D.
notableArchaeologicalSite
Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
-
E.
hasArchaeologicalSiteType
Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 6:42 a.m.