Triple
T4057942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yusuf |
E84738
|
entity |
| Predicate | roleInEgypt |
P24057
|
FINISHED |
| Object | high official |
—
|
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: high official | Statement: [Yusuf, roleInEgypt, high official]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEgypt Context triple: [Yusuf, roleInEgypt, high official]
-
A.
statusInEgypt
chosen
Indicates the legal, social, or official condition or standing that an entity holds specifically within the context of Egypt.
-
B.
roleInMedina
Indicates the specific function, position, or responsibility an entity holds within the context of Medina.
-
C.
roleInIsrael
Indicates that an entity holds or held a specific role, position, or function within the context of Israel.
-
D.
associatedWithPharaoh
Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
-
E.
objectiveOfEgypt
Indicates that something is the goal, aim, or intended outcome pursued by Egypt.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbaefcb081908aab3963dcd61a20 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.