Triple
T33244985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Muwaffaq |
E851071
|
entity |
| Predicate | laterBaseOfPower |
P102524
|
FINISHED |
| Object | Baghdad |
—
|
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: Baghdad | Statement: [al-Muwaffaq, laterBaseOfPower, Baghdad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBaseOfPower Context triple: [al-Muwaffaq, laterBaseOfPower, Baghdad]
-
A.
laterBase
Indicates that one event, state, or version occurs or is valid at a later time than another referenced event, state, or version.
-
B.
laterPowerBaseShiftedTo
chosen
Indicates that the primary base of power or influence for an entity moved from one location or group to another at a subsequent time.
-
C.
laterPowerType
Indicates that one entity represents a power type that occurs or is defined at a later stage or level relative to another power type.
-
D.
hasPowerBase
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
E.
basedOnPowersOf
Indicates a relationship where one quantity, structure, or concept is defined, derived, or constructed using powers (exponents) of 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: May 1, 2026, 1:31 a.m.