Triple
T9718830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merimde Beni Salama |
E235409
|
entity |
| Predicate | excavationResumedIn |
P44052
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Merimde Beni Salama, excavationResumedIn, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavationResumedIn Context triple: [Merimde Beni Salama, excavationResumedIn, 1970s]
-
A.
excavationResumed
chosen
Indicates that a previously halted excavation activity has been started again.
-
B.
excavatedAfter
Indicates that one excavation event occurred later in time than another excavation event.
-
C.
excavationEnd
Indicates the point in time or event at which an excavation activity is completed or brought to an end.
-
D.
excavatedFor
Indicates that something has been dug out or uncovered from the ground specifically for the benefit, use, or purpose of another entity.
-
E.
excavationIntensified
Indicates that the level or extent of excavation activity has increased in intensity compared to a previous state or period.
- 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_69ca84d0123c819096f9dc3b6abb0881 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e4022c4819097455f14dd9b1a77 |
completed | April 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:20 p.m.