Triple
T13378943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geshem the Arab |
E319263
|
entity |
| Predicate | opposedLeaderOf |
P19546
|
FINISHED |
| Object | returned Judean community |
—
|
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: returned Judean community | Statement: [Geshem the Arab, opposedLeaderOf, returned Judean community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedLeaderOf Context triple: [Geshem the Arab, opposedLeaderOf, returned Judean community]
-
A.
opposedLeader
chosen
Indicates that one entity actively resisted, challenged, or worked against the leadership or authority of another entity.
-
B.
primaryOpposingLeader
Indicates that one entity serves as the main or chief leader directly opposing another entity in a conflict, competition, or political context.
-
C.
oppositionLeader
Indicates that one entity serves as the primary political leader of the opposition in relation to another governing entity.
-
D.
mainOpposingPolitician
Indicates that one politician is the primary political rival or adversary of another.
-
E.
opposedByLeader
Indicates that an action, proposal, or position is actively resisted or rejected by a leader.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce56c6c8190adf4e19f6d1bc233 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.