Triple
T31882199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laish |
E813910
|
entity |
| Predicate | politicalStatusInJudges |
P50731
|
FINISHED |
| Object | isolated and lacking allies |
—
|
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: isolated and lacking allies | Statement: [Laish, politicalStatusInJudges, isolated and lacking allies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusInJudges Context triple: [Laish, politicalStatusInJudges, isolated and lacking allies]
-
A.
socialStatusOfJudges
Indicates the social standing or rank held by judges within a given society or context.
-
B.
politicalStatusContext
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
-
C.
statusInJudges
chosen
Indicates that an entity holds a particular role, position, or standing within a group or body of judges.
-
D.
politicalStatusRepresented
Indicates that an entity’s political status is expressed, symbolized, or officially represented by another entity.
-
E.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 30, 2026, 11:56 p.m.