Triple
T2936361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazor |
E79278
|
entity |
| Predicate | reoccupiedIn |
P44051
|
FINISHED |
| Object | Iron Age I |
—
|
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: Iron Age I | Statement: [Hazor, reoccupiedIn, Iron Age I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reoccupiedIn Context triple: [Hazor, reoccupiedIn, Iron Age I]
-
A.
reoccupiedByUnionForces
Indicates that a location previously held by Union forces was retaken and brought back under Union military control.
-
B.
occupies
Indicates that one entity takes up or resides within a physical or conceptual space belonging to or associated with another entity.
-
C.
occupyingPower
Indicates that one entity holds military or political control over a territory that it does not legally own, typically as an occupying authority.
-
D.
occupiedFrom
Indicates that an entity is in use or inhabited starting from a specified point in time.
-
E.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
- F. None of above. chosen
Provenance (4 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983df5e08190939cd8acf8ad5b55 |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:56 p.m.