Triple
T21573254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mansabdars |
E532334
|
entity |
| Predicate | sawarIndicates |
P144308
|
FINISHED |
| Object | cavalry obligations |
—
|
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: cavalry obligations | Statement: [mansabdars, sawarIndicates, cavalry obligations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawarIndicates Context triple: [mansabdars, sawarIndicates, cavalry obligations]
-
A.
sawServiceIn
Indicates that an entity observed or experienced a particular service within a specified context, location, or timeframe.
-
B.
sawServiceDuring
Indicates that one entity experienced or utilized a service during the time period associated with another entity or event.
-
C.
sawProcess
Indicates that an entity observed or witnessed a particular process or sequence of actions.
-
D.
sawCombatant
Indicates that one entity directly observed or witnessed another entity who is engaged as a combatant in a conflict or battle.
-
E.
sawActionDuring
Indicates that one entity observed an action or event occurring within a specific time period or during another event.
- 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_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. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:30 p.m.