Triple
T34785681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samaniyya order |
E1002797
|
entity |
| Predicate | spreadsThrough |
P113650
|
FINISHED |
| Object | missionary activity |
—
|
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: missionary activity | Statement: [Samaniyya order, spreadsThrough, missionary activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spreadsThrough Context triple: [Samaniyya order, spreadsThrough, missionary activity]
-
A.
spreadsAs
Indicates that one entity propagates, extends, or disseminates from another entity or source.
-
B.
propagates
Indicates that something causes itself, its effects, or its characteristics to spread or be transmitted from one entity, location, or state to others.
-
C.
spreadingMechanism
chosen
Indicates how something propagates or is transmitted from one entity, location, or medium to another.
-
D.
spreadingStatus
Indicates the current state or progression of how something is spreading or being disseminated (e.g., whether and how it is expanding, stable, or declining).
-
E.
spreadTo
Indicates that something extends, propagates, or is transmitted from one entity, location, or context to another.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.