Triple
T16193251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prophet Yusuf |
E392994
|
entity |
| Predicate | raisedToPosition |
P109561
|
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 Yusuf, raisedToPosition, authority in Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisedToPosition Context triple: [Prophet Yusuf, raisedToPosition, authority in Egypt]
-
A.
raisedTo
chosen
Indicates that one entity has been elevated, lifted, or brought up to a higher level, position, or state by another entity.
-
B.
raisedDuring
Indicates that one entity was brought up, nurtured, or developed within the time period or circumstances defined by another entity.
-
C.
raisedFrom
Indicates that one entity has been elevated, derived, or brought up from another prior state, source, or condition.
-
D.
raisedWith
Indicates that two or more entities grew up together in the same household or close environment during their formative years.
-
E.
raisedAt
Indicates that something was brought up, mentioned, or initiated at a particular time, place, or contextual point.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222d74d788190a637fdb9b4f184b9 |
completed | April 17, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.