Triple
T21573253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mansabdars |
E532334
|
entity |
| Predicate | zatIndicates |
P72041
|
FINISHED |
| Object | personal rank of the officer |
—
|
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: personal rank of the officer | Statement: [mansabdars, zatIndicates, personal rank of the officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zatIndicates Context triple: [mansabdars, zatIndicates, personal rank of the officer]
-
A.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
B.
labelIndication
Indicates that a label or designation is assigned to an entity to specify its indication, purpose, or intended use.
-
C.
canIndicate
chosen
Indicates that one entity has the potential or capacity to serve as a sign, signal, or evidence of another entity or condition.
-
D.
canAlsoIndicate
Indicates that something may additionally signify, represent, or serve as another meaning or function beyond its primary one.
-
E.
indicatedFor
Indicates...that one entity (typically a treatment, procedure, or product) is recommended or appropriate for use in relation to another entity (such as a condition, symptom, or patient group).
- 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.