Triple
T14805856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenician shophet |
E348031
|
entity |
| Predicate | exercisedPowerWith |
P115797
|
FINISHED |
| Object | city council |
—
|
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: city council | Statement: [Phoenician shophet, exercisedPowerWith, city council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exercisedPowerWith Context triple: [Phoenician shophet, exercisedPowerWith, city council]
-
A.
exercisedPowerFrom
Indicates that one entity exerted authority, control, or influence originating from a particular source, position, or location over another entity or context.
-
B.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
C.
typeOfPowerExercised
Indicates the specific kind or nature of power or authority that is being exercised in a given relationship or context.
-
D.
exerciseOfPower
Indicates the exertion or application of authority, control, or influence by one entity over another or within a given context.
-
E.
hadExecutivePowerIn
Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf32666081908e84f985c47eb963 |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:34 a.m.