Triple
T31419951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palmyrene royal house |
E801501
|
entity |
| Predicate | emergedAsPower |
P8145
|
FINISHED |
| Object | after mid-3rd century CE |
—
|
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: after mid-3rd century CE | Statement: [Palmyrene royal house, emergedAsPower, after mid-3rd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergedAsPower Context triple: [Palmyrene royal house, emergedAsPower, after mid-3rd century CE]
-
A.
successorAsRegionalPower
Indicates that one entity has replaced another as the dominant or leading power within a particular region.
-
B.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
C.
cameToPowerIn
chosen
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
D.
cameToPowerThrough
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
E.
madeMajorPower
Indicates that one entity caused or enabled another entity to attain the status or influence of a major power.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:47 p.m.