Triple
T4790565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptolemy V Epiphanes |
E106589
|
entity |
| Predicate | alsoRuledAs |
P21629
|
FINISHED |
| Object | Macedonian king 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: Macedonian king in Egypt | Statement: [Ptolemy V Epiphanes, alsoRuledAs, Macedonian king in Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoRuledAs Context triple: [Ptolemy V Epiphanes, alsoRuledAs, Macedonian king in Egypt]
-
A.
alsoRuled
chosen
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
B.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
C.
alsoKingOf
Indicates that an entity who is king of one place is simultaneously king of another place as well.
-
D.
laterUnderRuleOf
Indicates that one entity came to be governed or ruled by another entity at a later point in time.
-
E.
dynastyRuled
Indicates that a particular dynasty held ruling authority or governance over a specified region, state, or people during a certain period.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65dce6888190a0b1bdf416fb62b9 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.