Triple
T21573572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manat |
E532340
|
entity |
| Predicate | religiousStatusAfterIslam |
P87140
|
FINISHED |
| Object | considered pagan deity |
—
|
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: considered pagan deity | Statement: [Manat, religiousStatusAfterIslam, considered pagan deity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousStatusAfterIslam Context triple: [Manat, religiousStatusAfterIslam, considered pagan deity]
-
A.
statusAfterIslam
chosen
Indicates the state or condition an entity has after adopting or entering into Islam, as contrasted with its prior status.
-
B.
religiousStatus
Indicates the religious affiliation, role, or standing that an entity holds within a religious context.
-
C.
politicalStatusPreIslam
Indicates the political condition, role, or organization that existed before the advent or establishment of Islam.
-
D.
convertedToIslamWith
Indicates that one entity adopted Islam through the influence, guidance, or involvement of another entity.
-
E.
religiousAffiliationLater
Indicates that an entity’s religious affiliation at a later time is the specified religion or organization.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cef2748190990a81967d49b706 |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.