Triple
T7051769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prophet Joseph |
E163982
|
entity |
| Predicate | roseToPosition |
P61030
|
FINISHED |
| Object | authority in Egypt |
—
|
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: authority in Egypt | Statement: [Prophet Joseph, roseToPosition, authority in Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roseToPosition Context triple: [Prophet Joseph, roseToPosition, authority in Egypt]
-
A.
roseToPowerIn
Indicates the point in time or context in which an entity gained authority, control, or a dominant position.
-
B.
roseToProminenceUnder
Indicates that an entity became well-known, influential, or successful during the period of another entity’s leadership, guidance, or dominance.
-
C.
roseToProminenceIn
Indicates the time or context in which an entity became widely recognized, influential, or notable.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
ascendedTo
chosen
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.