Triple
T21573255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mansabdars |
E532334
|
entity |
| Predicate | obligedToMaintain |
P6254
|
FINISHED |
| Object | cavalrymen |
—
|
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: cavalrymen | Statement: [mansabdars, obligedToMaintain, cavalrymen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obligedToMaintain Context triple: [mansabdars, obligedToMaintain, cavalrymen]
-
A.
soughtToMaintain
Indicates an entity’s deliberate effort or intention to keep another entity or condition in its existing state over time.
-
B.
obligation
chosen
Indicates that one entity is bound or required to perform a duty, action, or fulfill a condition toward another entity or according to a rule or agreement.
-
C.
isObligatory
Indicates that an entity is required or must be performed, fulfilled, or complied with according to some rule, norm, or obligation.
-
D.
canMaintain
Indicates that one entity has the ability or capacity to maintain, service, or keep another entity in proper working condition.
-
E.
coreObligation
Indicates that one entity has a primary, essential duty or responsibility owed to another entity or with respect to a particular action or state.
- 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.