Triple
T28936956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umayyad army |
E730342
|
entity |
| Predicate | supplySystem |
P49241
|
FINISHED |
| Object | diwan-based pay registers |
—
|
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: diwan-based pay registers | Statement: [Umayyad army, supplySystem, diwan-based pay registers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supplySystem Context triple: [Umayyad army, supplySystem, diwan-based pay registers]
-
A.
supplySituation
Indicates a relationship where one entity provides or makes available needed resources, goods, or services to another under specific conditions or circumstances.
-
B.
supplyType
chosen
Indicates the kind or category of supply associated with or provided in a given relationship or context.
-
C.
supplyBy
Indicates that one entity is provided, furnished, or made available by another entity as its source or supplier.
-
D.
supplyMode
Indicates the manner or method by which something is provided, delivered, or made available.
-
E.
supplyLine
Indicates a logistical connection through which resources, goods, or support are transported from a source to a destination.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 8:33 a.m.