Triple
T3328430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magdala |
E69972
|
entity |
| Predicate | governedDuringPeriod |
P47315
|
FINISHED |
| Object | Herodian rule |
—
|
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: Herodian rule | Statement: [Magdala, governedDuringPeriod, Herodian rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedDuringPeriod Context triple: [Magdala, governedDuringPeriod, Herodian rule]
-
A.
governedForMostOfPeriodSince
Indicates that one entity has held governing authority over another for the majority of a specified time period since a given starting point.
-
B.
governedByAtTimeOfEvent
Indicates that an entity is under the authority or control of a particular governing agent specifically at the time a given event occurs.
-
C.
governedAs
Indicates that one entity exercises authoritative control, direction, or rule over another according to some system of governance or leadership.
-
D.
governedFrom
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
-
E.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1708b908190bc5c4122623d9b77 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:12 p.m.