Triple
T2291212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Ma'mun |
E51505
|
entity |
| Predicate | ledCampaignsIn |
P19922
|
FINISHED |
| Object | Byzantine frontier regions |
—
|
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: Byzantine frontier regions | Statement: [al-Ma'mun, ledCampaignsIn, Byzantine frontier regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledCampaignsIn Context triple: [al-Ma'mun, ledCampaignsIn, Byzantine frontier regions]
-
A.
ledCampaignIn
chosen
Indicates that an entity directed or was in charge of organizing and executing a campaign within a particular context or location.
-
B.
campaignType
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
C.
socialMediaPlatformLed
Indicates that one entity has taken a leadership or primary driving role in the development, direction, or success of a social media platform.
-
D.
campaignOrService
Indicates that one entity is a campaign and the other is a service that the campaign promotes, uses, or is associated with.
-
E.
testCampaign
Indicates that an entity is involved in or associated with a campaign conducted for testing, experimentation, or evaluation purposes.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:48 p.m.