Triple
T31625643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syrian Arab tribes |
E807015
|
entity |
| Predicate | declinedInInfluenceDuring |
P2924
|
FINISHED |
| Object | Abbasid period |
—
|
NE NERFINISHED |
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: Abbasid period | Statement: [Syrian Arab tribes, declinedInInfluenceDuring, Abbasid period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declinedInInfluenceDuring Context triple: [Syrian Arab tribes, declinedInInfluenceDuring, Abbasid period]
-
A.
declineIn
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
-
B.
declineAfter
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
C.
declinedDuring
chosen
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
D.
declineBeganUnder
Indicates that a period of decline started during the tenure, rule, or administration of a specified entity.
-
E.
declineTriggeredBy
Indicates that a decline event or state is caused or initiated by a specified triggering factor or condition.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8dfcc708190b19e7444a14cdbb9 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:43 p.m.