Triple
T36001818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darajat (degrees of Paradise) |
E1041151
|
entity |
| Predicate | hasHighRankAssociatedWith |
P199828
|
FINISHED |
| Object | prophets |
—
|
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: prophets | Statement: [Darajat (degrees of Paradise), hasHighRankAssociatedWith, prophets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighRankAssociatedWith Context triple: [Darajat (degrees of Paradise), hasHighRankAssociatedWith, prophets]
-
A.
associatedWithRank
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
B.
isHighRanking
Indicates that an entity holds a position of relatively great authority, status, or seniority within a hierarchy or organization.
-
C.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
D.
higherRankHas
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
E.
typicallyHoldsRank
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
- F. None of above. chosen
Provenance (4 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
| PDg | Predicate description generation | batch_69ff59b1e2ac8190bb65529e9dbbb178 |
completed | May 9, 2026, 3:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.