Triple
T21573270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mansabdars |
E532334
|
entity |
| Predicate | higherRankIndicates |
P39281
|
FINISHED |
| Object | greater status |
—
|
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: greater status | Statement: [mansabdars, higherRankIndicates, greater status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherRankIndicates Context triple: [mansabdars, higherRankIndicates, greater status]
-
A.
higherRankHas
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
B.
higherRankDescription
chosen
Indicates that one entity holds a superior or more senior rank or status compared to another entity.
-
C.
higherValueIndicates
Indicates that a greater numerical or qualitative value of one entity corresponds to a stronger presence, importance, or intensity of a specified property or outcome relative to another.
-
D.
highestRanking
Indicates that one entity holds the top or most senior rank relative to a set of other entities.
-
E.
rankIndicated
Indicates that one entity specifies, denotes, or reveals the hierarchical rank or level of another entity.
- 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_69eee9ce230c81909e12bd59497e2237 |
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.