Triple
T7372973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peribsen |
E170053
|
entity |
| Predicate | breaksWithTradition |
P40216
|
FINISHED |
| Object | Horus-centered royal titulary |
—
|
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: Horus-centered royal titulary | Statement: [Peribsen, breaksWithTradition, Horus-centered royal titulary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksWithTradition Context triple: [Peribsen, breaksWithTradition, Horus-centered royal titulary]
-
A.
breaksWith
chosen
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
B.
breakType
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
C.
break
Indicates that one entity causes another entity to separate into pieces, stop functioning, or otherwise lose its normal integrity or continuity.
-
D.
breakthrough
Indicates a significant and often sudden advance or discovery that overcomes a major obstacle in a process, field, or endeavor.
-
E.
establishedTradition
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1a50898819087097a64e09e19eb |
completed | March 27, 2026, 9:07 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:07 p.m.