Triple
T18992446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagid house |
E464721
|
entity |
| Predicate | usedRoyalCult |
P127798
|
FINISHED |
| Object | Ptolemaic ruler cult |
—
|
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: Ptolemaic ruler cult | Statement: [Lagid house, usedRoyalCult, Ptolemaic ruler cult]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRoyalCult Context triple: [Lagid house, usedRoyalCult, Ptolemaic ruler cult]
-
A.
royalUse
chosen
Indicates that something is used, employed, or reserved specifically by or for a royal person or royal institution.
-
B.
royalVariant
Indicates a relationship where one entity is a special or modified version of another that is associated with royalty, nobility, or regal status.
-
C.
royalNomen
Indicates that an entity bears a royal name or official titulary associated with monarchy or sovereign status.
-
D.
hasRoyalCircle
Indicates that an entity belongs to, is part of, or is associated with a royal or monarch’s inner circle or court.
-
E.
postRoyalUse
Indicates that something is used or occurs after a royal event, status, or period has ended.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d67eedc88190bfb7b327b47db76d |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.