Triple
T6780296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masyumi |
E155662
|
entity |
| Predicate | hadStrongSupportAmong |
P1704
|
FINISHED |
| Object | modernist Muslims |
—
|
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: modernist Muslims | Statement: [Masyumi, hadStrongSupportAmong, modernist Muslims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadStrongSupportAmong Context triple: [Masyumi, hadStrongSupportAmong, modernist Muslims]
-
A.
cameToPowerWithSupportFrom
Indicates that an entity attained a position of power or authority aided or enabled by the backing, assistance, or endorsement of another entity.
-
B.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
C.
strongestSupportRegion
Indicates the region where an entity receives its highest level of support compared to all other regions.
-
D.
dissolvedInFavorOf
Indicates that one entity has been formally terminated, annulled, or discontinued in order to benefit, support, or be replaced by another entity.
-
E.
receivedSupportFrom
chosen
Indicates that one entity obtained help, resources, or backing from another entity.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26b32c0819093f86b1002260660 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.